Triple
T23148935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servian reforms |
E578268
|
entity |
| Predicate | votingConsequence |
P10095
|
FINISHED |
| Object | political dominance of wealthy citizens |
—
|
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: political dominance of wealthy citizens | Statement: [Servian reforms, votingConsequence, political dominance of wealthy citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingConsequence Context triple: [Servian reforms, votingConsequence, political dominance of wealthy citizens]
-
A.
violationConsequences
Indicates the negative outcomes, penalties, or repercussions that result from a violation of a rule, law, or agreement.
-
B.
voteResult
chosen
Indicates the outcome or decision produced by a voting process involving the related entities.
-
C.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
D.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
E.
voteProcess
Indicates the formal procedure by which participants cast and record their votes to reach a decision or outcome.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ed0b76c8190ac61b949d88e9970 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.