Triple
T28119314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epaphroditus |
E710731
|
entity |
| Predicate | eventFollowedBy |
P165425
|
FINISHED |
| Object | accession of Galba |
—
|
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: accession of Galba | Statement: [Epaphroditus, eventFollowedBy, accession of Galba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventFollowedBy Context triple: [Epaphroditus, eventFollowedBy, accession of Galba]
-
A.
followerEvent
Indicates that one entity begins or performs the action of following another entity, typically recorded as a discrete event in time.
-
B.
eraFollowed
Indicates that one historical era comes directly after another in chronological sequence.
-
C.
eventDistribution
Indicates how occurrences of an event are spread or allocated across different times, locations, or categories.
-
D.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
E.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
- F. None of above. chosen
Provenance (4 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 9:16 p.m.