Triple
T33048852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flamines |
E845669
|
entity |
| Predicate | highestOfficeAmong |
P98376
|
FINISHED |
| Object | flamen Dialis |
—
|
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: flamen Dialis | Statement: [flamines, highestOfficeAmong, flamen Dialis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestOfficeAmong Context triple: [flamines, highestOfficeAmong, flamen Dialis]
-
A.
isHighestOfficeIn
chosen
Indicates that one office or position is the most senior or supreme authority within a specified organization, jurisdiction, or domain.
-
B.
heldHighestOfficeIn
Indicates that one entity occupied the most senior or supreme official position within the other entity (such as a country, organization, or jurisdiction).
-
C.
topPoliticalOffice
Indicates that the subject holds or is associated with the highest-ranking political office within a given governmental or political system.
-
D.
highestOrgan
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
-
E.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:24 a.m.