Triple
T20237111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octavius Caesar |
E498178
|
entity |
| Predicate | futureTitleInPlayWorld |
P117048
|
FINISHED |
| Object | first Roman emperor |
—
|
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: first Roman emperor | Statement: [Octavius Caesar, futureTitleInPlayWorld, first Roman emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureTitleInPlayWorld Context triple: [Octavius Caesar, futureTitleInPlayWorld, first Roman emperor]
-
A.
futureTitleInStory
chosen
Indicates that an entity will hold a specified title or role at a later point in the narrative timeline of the story.
-
B.
futureSiteOf
Indicates that a location is planned or designated to become the site of a particular entity or structure in the future.
-
C.
futureProgramme
Indicates that a programme is scheduled to occur at a future time relative to a given reference point.
-
D.
futureHeir
Indicates that one entity is designated or expected to inherit from another entity at a future time.
-
E.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716a5af0819095ea419a4d1f0d1d |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.