Triple
T37551647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forge of Souls |
E933602
|
entity |
| Predicate | followsContent |
P134
|
FINISHED |
| Object | level 80 Wrath of the Lich King dungeons |
—
|
LITERAL FINISHED |
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: level 80 Wrath of the Lich King dungeons | Statement: [Forge of Souls, followsContent, level 80 Wrath of the Lich King dungeons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsContent Context triple: [Forge of Souls, followsContent, level 80 Wrath of the Lich King dungeons]
-
A.
followsDisc
Indicates that one entity comes after another in a sequence or order, typically in a discrete or stepwise progression.
-
B.
follows
chosen
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
C.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
D.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
E.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
- 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_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.