Triple
T5047022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesarius of Arles |
E113690
|
entity |
| Predicate | startTime_positionHeld_BishopOfArles |
P60861
|
FINISHED |
| Object | 502 |
—
|
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: 502 | Statement: [Caesarius of Arles, startTime_positionHeld_BishopOfArles, 502]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTime_positionHeld_BishopOfArles Context triple: [Caesarius of Arles, startTime_positionHeld_BishopOfArles, 502]
-
A.
startTimeAtBishopOfSpeyer
Indicates the time at which an entity begins serving in the role of Bishop of Speyer.
-
B.
startTimeAsArchbishopOfMilan
Indicates the date and time when an individual began serving as Archbishop of Milan.
-
C.
currentArchbishopStartYear
Indicates the calendar year in which the current archbishop began serving in that role.
-
D.
firstBishop
Indicates that one entity is the first bishop (earliest in time or rank) associated with or holding episcopal authority over another entity.
-
E.
endTimeAtBishopOfSpeyer
Indicates that a time-bounded role, event, or state concludes at the point when the entity becomes (or ceases to be) the Bishop of Speyer.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd740002b48190bc7aa176d734c589 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:37 p.m.