Triple
T37599866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draenor |
E935492
|
entity |
| Predicate | notableOrcClans |
P111063
|
FINISHED |
| Object | Frostwolf clan |
E932342
|
NE 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: Frostwolf clan | Statement: [Draenor, notableOrcClans, Frostwolf clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOrcClans Context triple: [Draenor, notableOrcClans, Frostwolf clan]
-
A.
notableClans
chosen
Indicates that there exists a significant or historically important clan associated with the subject.
-
B.
clanOrKingdom
Indicates a relationship where an entity is associated with, belongs to, or is part of a particular clan or kingdom.
-
C.
notableWarriorSociety
Indicates that an entity is recognized as a prominent or historically significant warrior group or martial society.
-
D.
notableClanOrigin
Indicates that an entity is notably associated with originating from, belonging to, or being historically linked to a particular clan.
-
E.
ethnicOrMythicGroup
Indicates that an entity is associated with, belongs to, or is characterized by a particular ethnic group or mythic (legendary or folkloric) group.
- F. None of above.
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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40ba43c8cc81908d338d11c0f8ee85 |
completed | June 28, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.