Triple
T38644019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightborne |
E938670
|
entity |
| Predicate | chronologyEvent |
P140037
|
FINISHED |
| Object | Suramar rebellion against the Legion |
—
|
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: Suramar rebellion against the Legion | Statement: [Nightborne, chronologyEvent, Suramar rebellion against the Legion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyEvent Context triple: [Nightborne, chronologyEvent, Suramar rebellion against the Legion]
-
A.
chronologicallyNotableEvent
Indicates that an event is significant or noteworthy in terms of its position or impact within a chronological sequence of events.
-
B.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
C.
chronologicalPoint
Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
-
D.
chronologyIn
chosen
Indicates that one event or temporal entity occurs within the chronological scope or timeframe defined by another.
-
E.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:32 p.m.