Triple
T25075699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hallowed Hunt |
E628041
|
entity |
| Predicate | precedesInUniverse |
P160842
|
FINISHED |
| Object | Paladin of Souls |
—
|
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: Paladin of Souls | Statement: [The Hallowed Hunt, precedesInUniverse, Paladin of Souls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesInUniverse Context triple: [The Hallowed Hunt, precedesInUniverse, Paladin of Souls]
-
A.
precedesInUniverse
chosen
Indicates that one event or entity occurs earlier than another within the timeline or causal order of a given fictional or conceptual universe.
-
B.
chronologyPrecedes
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
C.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
-
D.
precedesDisc
Indicates that one discourse segment or unit occurs before another in the sequence of discourse.
-
E.
precedesInCareer
Indicates that one entity’s role, position, or stage in a professional path occurs earlier in time than another entity’s corresponding role, position, or stage in that same career trajectory.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 6:21 a.m.