Triple
T35125466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Agapetus I |
E1014289
|
entity |
| Predicate | GordianusOccupation |
P39445
|
FINISHED |
| Object | Roman priest |
—
|
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: Roman priest | Statement: [Pope Agapetus I, GordianusOccupation, Roman priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GordianusOccupation Context triple: [Pope Agapetus I, GordianusOccupation, Roman priest]
-
A.
roleInRome
chosen
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
B.
roleInGermanicusDeathNarrative
Indicates that one entity plays a specified role in the narrative account of Germanicus’s death.
-
C.
otherProtagonistOccupation
Indicates that another main character in the narrative has a specific occupation or job role.
-
D.
antagonistOccupation
Indicates the role, job, or professional activity that the antagonist character performs.
-
E.
roleInSyriana
Indicates that one entity has a specific role or involvement in the context of "Syriana," such as participation, function, or contribution related to it.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.