Triple
T37872644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of Fear |
E944642
|
entity |
| Predicate | progressionOrder |
P189158
|
FINISHED |
| Object | Tier 14 progression raid |
—
|
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: Tier 14 progression raid | Statement: [Heart of Fear, progressionOrder, Tier 14 progression raid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progressionOrder Context triple: [Heart of Fear, progressionOrder, Tier 14 progression raid]
-
A.
progressionPosition
chosen
Indicates the specific place or rank that something occupies within an ordered sequence, series, or progression.
-
B.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
C.
growthOrder
Indicates the sequential or hierarchical order in which growth or development occurs relative to other entities or stages.
-
D.
progressionModel
Indicates a model that represents how something changes, develops, or advances over time or through a sequence of stages.
-
E.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:19 p.m.