Triple
T8312208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valentia |
E194615
|
entity |
| Predicate | governingOfficial |
P60156
|
FINISHED |
| Object | praeses |
—
|
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: praeses | Statement: [Valentia, governingOfficial, praeses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingOfficial Context triple: [Valentia, governingOfficial, praeses]
-
A.
governingHead
Indicates that one entity serves as the ruling or administrative authority over another entity, acting as its primary leader or head.
-
B.
governmentBodyOccupant
Indicates that a person holds an official position or role within a particular government body or institution.
-
C.
headOfGovernmentBody
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
-
D.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
E.
governingOffice
chosen
Indicates the official position or office through which an entity exercises governing authority over a jurisdiction or organization.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f504ca8819087fb1f731f7a7cfd |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.