Triple
T37509107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords of Dread |
E932171
|
entity |
| Predicate | precedesEncounter |
P160842
|
FINISHED |
| Object | Rygelon |
—
|
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: Rygelon | Statement: [Lords of Dread, precedesEncounter, Rygelon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesEncounter Context triple: [Lords of Dread, precedesEncounter, Rygelon]
-
A.
hasEncounter
Indicates that one entity experiences or comes into contact with another entity or event, typically in a specific context or situation.
-
B.
precedesDisc
Indicates that one discourse segment or unit occurs before another in the sequence of discourse.
-
C.
precedesFeature
Indicates that one feature occurs, is implemented, or is introduced before another feature in a defined sequence or timeline.
-
D.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
-
E.
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.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:17 p.m.