Triple
T37592187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frostwyrm Lair |
E935286
|
entity |
| Predicate | basedOnLocationFrom |
P54922
|
FINISHED |
| Object | World of Warcraft |
—
|
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: World of Warcraft | Statement: [Frostwyrm Lair, basedOnLocationFrom, World of Warcraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnLocationFrom Context triple: [Frostwyrm Lair, basedOnLocationFrom, World of Warcraft]
-
A.
basedOnBy
chosen
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
C.
basedInSetting
Indicates that an entity is situated, located, or primarily operates within a particular setting or environment.
-
D.
basedOnLongitudeOf
Indicates that one entity’s position, value, or determination is derived from or defined with respect to the longitude of another entity.
-
E.
locationProposedFrom
Indicates a proposed or suggested origin location from which something is expected or planned to come.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:18 p.m.