Triple
T38589236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Frostwing Halls |
E932414
|
entity |
| Predicate | containsEncounter |
P203906
|
FINISHED |
| Object | Valithria Dreamwalker encounter |
—
|
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: Valithria Dreamwalker encounter | Statement: [The Frostwing Halls, containsEncounter, Valithria Dreamwalker encounter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEncounter Context triple: [The Frostwing Halls, containsEncounter, Valithria Dreamwalker encounter]
-
A.
hasEncounter
Indicates that one entity experiences or comes into contact with another entity or event, typically in a specific context or situation.
-
B.
containsEncounterType
chosen
Indicates that one entity includes or encompasses a specific type or category of encounter within it.
-
C.
followsEncounter
Indicates that one encounter occurs after and in sequence with another encounter.
-
D.
encounterID
Indicates a unique identifier that links all data and events associated with a single encounter or interaction between entities.
-
E.
encounterOrder
Indicates the sequence in which entities meet or come into contact with each other.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02efcb13248190a0bef09ba7869ada |
completed | May 12, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_6a024995e1d081908783ca294d1397c3 |
completed | May 11, 2026, 9:26 p.m. |
Created at: May 3, 2026, 4:32 p.m.