Triple
T33847597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabic |
E867524
|
entity |
| Predicate | roleInEritrea |
P202685
|
FINISHED |
| Object | working language |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: working language | Statement: [Arabic, roleInEritrea, working language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEritrea Context triple: [Arabic, roleInEritrea, working language]
-
A.
roleInEstonia
Indicates that an entity holds or has held an official position, function, or role within Estonia.
-
B.
roleInGeorgia
Indicates that an entity holds or has held a specific role, position, or function within the context of Georgia (such as its government, institutions, or organizations).
-
C.
roleInAbyssinia
Indicates that an entity holds or held a specific role, position, or function in the context of Abyssinia (historical Ethiopia).
-
D.
roleInIsrael
Indicates that an entity holds or held a specific role, position, or function within the context of Israel.
-
E.
roleInEHT
Indicates that an entity holds a specific role or function within the Event Horizon Telescope (EHT) collaboration or project.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_6a00acf7923c819091ae7fbda05164f6 |
completed | May 10, 2026, 4:06 p.m. |
Created at: May 1, 2026, 1:47 a.m.