Triple
T31419792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corrector totius Orientis |
E801497
|
entity |
| Predicate | officeHolderTitleOf |
P85416
|
FINISHED |
| Object | Odaenathus |
—
|
NE NERFINISHED |
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: Odaenathus | Statement: [Corrector totius Orientis, officeHolderTitleOf, Odaenathus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderTitleOf Context triple: [Corrector totius Orientis, officeHolderTitleOf, Odaenathus]
-
A.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
B.
currentOfficeHolderTitle
Indicates the official title or position name held by the person who currently occupies a given office or role.
-
C.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
D.
typicalOfficeHolderTitle
chosen
Indicates the standard or commonly used title typically held by the office holder of a given position or role.
-
E.
residenceOfOfficeHolderTitle
Indicates the place where a person holding a particular official title resides while in that role.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: April 30, 2026, 8:47 p.m.