Triple
T28502719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Octavius (tribune of the plebs, 133 BC) |
E721277
|
entity |
| Predicate | usedPower |
P84381
|
FINISHED |
| Object | tribunician veto |
—
|
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: tribunician veto | Statement: [Marcus Octavius (tribune of the plebs, 133 BC), usedPower, tribunician veto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPower Context triple: [Marcus Octavius (tribune of the plebs, 133 BC), usedPower, tribunician veto]
-
A.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
B.
showsPowerUse
chosen
Indicates that one entity demonstrates or exercises power, influence, or control over another entity or within a given context.
-
C.
usesEnergy
Indicates that one entity consumes or relies on some form of energy to function, operate, or perform an action.
-
D.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
E.
airPowerUsedBy
Indicates that a particular actor employs or deploys air power (such as aircraft or aerial operations) as part of its activities or capabilities.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 3:07 a.m.