Triple
T38583116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightforged draenei |
E932288
|
entity |
| Predicate | racialQuestlineLocation |
P100057
|
FINISHED |
| Object | Argus |
—
|
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: Argus | Statement: [Lightforged draenei, racialQuestlineLocation, Argus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racialQuestlineLocation Context triple: [Lightforged draenei, racialQuestlineLocation, Argus]
-
A.
loreLocation
Indicates that something is the place or setting where related background story, history, or world-building information is situated or associated.
-
B.
associatedTribeLocation
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
-
C.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
D.
questlineFeature
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
E.
zoneQuestHub
chosen
Indicates a relationship where a particular zone serves as the central hub or main base for quests within a game or system.
- 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_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.