Triple
T29597205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethiopian Ambassador to Djibouti |
E754331
|
entity |
| Predicate | formalTitleLanguage |
P51323
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Ethiopian Ambassador to Djibouti, formalTitleLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalTitleLanguage Context triple: [Ethiopian Ambassador to Djibouti, formalTitleLanguage, English]
-
A.
officialTitleInLanguage
chosen
Indicates that an entity’s official title or designation is expressed in a specified language.
-
B.
officialLanguageOfTitle
Indicates that a specified language is the officially designated language associated with a particular title or position.
-
C.
titleLanguageForm
Indicates the specific linguistic form or variant in which a title is expressed (e.g., language, script, or transliteration form).
-
D.
formalTitleInLuxembourgish
Indicates that an entity holds a specific formal or official title expressed in the Luxembourgish language.
-
E.
usedInFormalTitleOf
Indicates that something is employed as part of the official or formal title of an entity.
- F. None of above.
Provenance (3 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:19 p.m.