Triple
T36091366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Killing Strangers |
E1043926
|
entity |
| Predicate | chronologicallyPartOf |
P194086
|
FINISHED |
| Object | The Pale Emperor era |
—
|
NE NERFINISHED |
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: The Pale Emperor era | Statement: [Killing Strangers, chronologicallyPartOf, The Pale Emperor era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyPartOf Context triple: [Killing Strangers, chronologicallyPartOf, The Pale Emperor era]
-
A.
chronologicallyBelongsTo
chosen
Indicates that one temporal entity or event falls within, or is properly associated with, a specific time period or chronological grouping.
-
B.
chronologicallyInvolvedIn
Indicates that an entity participates in or is associated with an event, process, or activity during a specific time period in a chronological sequence.
-
C.
chronologyPrecedes
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
D.
chronologyIncludes
Indicates that a broader chronological sequence or timeline encompasses a specific time span, event, or period as part of it.
-
E.
chronologicallyAfter
Indicates that one event or state occurs later in time than 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4:08 p.m.