Triple
T37872273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vale of Eternal Blossoms |
E944634
|
entity |
| Predicate | threatInPatch83 |
P172831
|
FINISHED |
| Object | N'Zoth |
—
|
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: N'Zoth | Statement: [Vale of Eternal Blossoms, threatInPatch83, N'Zoth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatInPatch83 Context triple: [Vale of Eternal Blossoms, threatInPatch83, N'Zoth]
-
A.
threatInStory
Indicates that one entity poses or represents a danger, menace, or harmful intent toward another entity within the context of a narrative or story.
-
B.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatEncounteredNear
chosen
Indicates that a threat was encountered in close spatial proximity to a specified reference point or entity.
-
D.
laterThreat
Indicates that one entity poses a threat to another at a time subsequent to some referenced or initial point.
-
E.
threatContained
Indicates that an identified threat has been successfully neutralized, controlled, or otherwise prevented from causing further harm or escalation.
- 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.