Triple
T37872047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Jade Forest |
E944630
|
entity |
| Predicate | introducesRaceLore |
P198842
|
FINISHED |
| Object | pandaren |
—
|
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: pandaren | Statement: [The Jade Forest, introducesRaceLore, pandaren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesRaceLore Context triple: [The Jade Forest, introducesRaceLore, pandaren]
-
A.
introducesRace
Indicates that one entity presents, initiates, or brings into existence a race, competition, or racial category involving another entity.
-
B.
races
Indicates that one entity competes in a speed-based contest or race against another entity.
-
C.
raceInLegendarium
Indicates that an entity belongs to a particular fictional race or species within a specific mythological or fantasy legendarium.
-
D.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
E.
cardRace
Indicates that one entity participates in or is associated with a competitive race involving cards or card-based vehicles relative to another entity.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69ff0d800ee88190835e233d9e846cdb |
completed | May 9, 2026, 10:33 a.m. |
Created at: May 3, 2026, 4:19 p.m.