Triple
T38644741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rut'theran Village |
E938685
|
entity |
| Predicate | raceStartingAreaFor |
P124147
|
FINISHED |
| Object | night elf characters |
—
|
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: night elf characters | Statement: [Rut'theran Village, raceStartingAreaFor, night elf characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceStartingAreaFor Context triple: [Rut'theran Village, raceStartingAreaFor, night elf characters]
-
A.
raceAdded
Indicates that a race event or race-related record has been newly created or incorporated into a system or dataset.
-
B.
raceStartType
Indicates the manner or format in which a race is initiated (e.g., type or method of starting the race).
-
C.
startedRacing
Indicates that an entity began participating in a racing activity or competition, marking the initiation of its involvement in racing.
-
D.
raceRecordStarts
Indicates that a race record begins or is initiated at a specific point or event in time.
-
E.
raceTrack
chosen
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.