Triple
T23985444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earthstrong of Haile Selassie I |
E604919
|
entity |
| Predicate | associatedTitleOfHonoree |
P58157
|
FINISHED |
| Object | Emperor of Ethiopia |
—
|
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: Emperor of Ethiopia | Statement: [Earthstrong of Haile Selassie I, associatedTitleOfHonoree, Emperor of Ethiopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTitleOfHonoree Context triple: [Earthstrong of Haile Selassie I, associatedTitleOfHonoree, Emperor of Ethiopia]
-
A.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
B.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
C.
alsoHonoredAs
chosen
Indicates that an entity is additionally recognized or celebrated under another title, role, or form of honor beyond its primary designation.
-
D.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
E.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2c10c708190922daf3b3b9555f4 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:32 p.m.