Triple
T9494007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarch of Ethiopia |
E228959
|
entity |
| Predicate | hasSymbolicTitle |
P88931
|
FINISHED |
| Object | head of the See of Saint Mark in 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: head of the See of Saint Mark in Ethiopia | Statement: [Patriarch of Ethiopia, hasSymbolicTitle, head of the See of Saint Mark in Ethiopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymbolicTitle Context triple: [Patriarch of Ethiopia, hasSymbolicTitle, head of the See of Saint Mark in Ethiopia]
-
A.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
B.
hasExplicitTitle
Indicates that an entity is associated with a clearly specified, formally stated title rather than an implicit or inferred one.
-
C.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
D.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
-
E.
hasTitleSubject
Indicates that an entity has a specific subject or topic as the focus of its title.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95e8c8908190950e1130f9612823 |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca8c6b0f081908334d6c7cf80e03c |
completed | April 1, 2026, 5:10 a.m. |
Created at: March 30, 2026, 7:56 p.m.