Triple
T35697406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servius Sulpicius Galba |
E1031477
|
entity |
| Predicate | roseToPowerBy |
P47710
|
FINISHED |
| Object | rebellion against Nero |
—
|
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: rebellion against Nero | Statement: [Servius Sulpicius Galba, roseToPowerBy, rebellion against Nero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseToPowerBy Context triple: [Servius Sulpicius Galba, roseToPowerBy, rebellion against Nero]
-
A.
roseToPowerIn
Indicates the point in time or context in which an entity gained authority, control, or a dominant position.
-
B.
roseToPowerInCentury
Indicates that an entity attained or began its dominant political or authoritative position during a specified century.
-
C.
methodOfRiseToPower
chosen
Indicates the manner, strategy, or process by which an entity attained power or authority.
-
D.
powersAscentOf
Indicates that one entity provides the driving force, energy, or enabling influence behind another entity’s rise, advancement, or upward progression.
-
E.
exponent
Indicates that one quantity is raised to the power of another, expressing repeated multiplication of a base by itself.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.