Triple
T37551648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forge of Souls |
E933602
|
entity |
| Predicate | precedesInstance |
P80614
|
FINISHED |
| Object | Pit of Saron |
—
|
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: Pit of Saron | Statement: [Forge of Souls, precedesInstance, Pit of Saron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesInstance Context triple: [Forge of Souls, precedesInstance, Pit of Saron]
-
A.
previousInstanceOf
Indicates that one entity is an earlier occurrence or version of another entity in a sequence or history.
-
B.
precedesFeature
Indicates that one feature occurs, is implemented, or is introduced before another feature in a defined sequence or timeline.
-
C.
precedesInStability
Indicates that one entity is more stable than another, coming earlier in an ordering based on stability.
-
D.
precedesInUniverse
Indicates that one event or entity occurs earlier than another within the timeline or causal order of a given fictional or conceptual universe.
-
E.
predecessorRelationship
chosen
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 3, 2026, 4:17 p.m.