Triple
T37539047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azuremyst Isle |
E933279
|
entity |
| Predicate | startingRace |
P203103
|
FINISHED |
| Object | Draenei |
—
|
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: Draenei | Statement: [Azuremyst Isle, startingRace, Draenei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingRace Context triple: [Azuremyst Isle, startingRace, Draenei]
-
A.
startedRacing
Indicates that an entity began participating in a racing activity or competition, marking the initiation of its involvement in racing.
-
B.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
-
C.
raceStartType
Indicates the manner or format in which a race is initiated (e.g., type or method of starting the race).
-
D.
raceRecordStarts
Indicates that a race record begins or is initiated at a specific point or event in time.
-
E.
frontRunnerAtStart
Indicates that an entity is the leading competitor or in first position at the beginning of an event or process.
- F. None of above. chosen
Provenance (4 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01203ac018819085d7c9abd8345b23 |
completed | May 11, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_6a011f3f149c819090749722da0e3413 |
completed | May 11, 2026, 12:13 a.m. |
| PDg | Predicate description generation | batch_6a01203a1c188190874d87d148dfa8e4 |
completed | May 11, 2026, 12:18 a.m. |
Created at: May 3, 2026, 4:17 p.m.