Triple
T37551746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borean Tundra |
E933604
|
entity |
| Predicate | questContentType |
P184907
|
FINISHED |
| Object | introductory Northrend storyline |
—
|
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: introductory Northrend storyline | Statement: [Borean Tundra, questContentType, introductory Northrend storyline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questContentType Context triple: [Borean Tundra, questContentType, introductory Northrend storyline]
-
A.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
B.
questContent
chosen
Indicates that one entity is the content, objective, or narrative substance of a quest associated with another entity.
-
C.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
-
D.
questionType
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
-
E.
requestType
Indicates the specific kind or category of request being made in an interaction or transaction.
- 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_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:17 p.m.