Triple
T8311902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribunes of the Plebs |
E194609
|
entity |
| Predicate | heldPower |
P544
|
FINISHED |
| Object | right of veto (intercessio) |
—
|
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: right of veto (intercessio) | Statement: [Tribunes of the Plebs, heldPower, right of veto (intercessio)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldPower Context triple: [Tribunes of the Plebs, heldPower, right of veto (intercessio)]
-
A.
heldTemporalPower
Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
-
B.
hasPower
chosen
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
D.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
E.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
- 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.