Triple
T37550935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lok'tar ogar |
E933587
|
entity |
| Predicate | fandomRecognition |
P38677
|
FINISHED |
| Object | iconic Warcraft quote |
—
|
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: iconic Warcraft quote | Statement: [Lok'tar ogar, fandomRecognition, iconic Warcraft quote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fandomRecognition Context triple: [Lok'tar ogar, fandomRecognition, iconic Warcraft quote]
-
A.
fandomSignificance
Indicates the degree to which something holds importance, influence, or prominence within a particular fan community or fandom context.
-
B.
fandomScope
Indicates the extent or boundaries of a fandom-related relationship, such as how broadly or narrowly a fan’s interest, participation, or recognition applies.
-
C.
fandomUses
Indicates that a fandom makes use of, relies on, or incorporates a particular resource, tool, platform, or element.
-
D.
fandomReception
chosen
Indicates how a work, character, or creator is perceived, evaluated, and responded to by its fan community.
-
E.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.