Triple
T37592018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Kurast |
E935282
|
entity |
| Predicate | hasQuestAccess |
P182182
|
FINISHED |
| Object | The Blackened Temple |
—
|
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: The Blackened Temple | Statement: [Upper Kurast, hasQuestAccess, The Blackened Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuestAccess Context triple: [Upper Kurast, hasQuestAccess, The Blackened Temple]
-
A.
hasQuestHubIn
Indicates that a quest hub is located within or associated with a particular place or region.
-
B.
hasQuestElement
Indicates that something is a component, step, or requirement that forms part of a larger quest or mission.
-
C.
hasQuestContentIn
chosen
Indicates that a quest’s narrative or objectives are contained within or associated with a particular location, context, or container.
-
D.
hasQuestHubRole
Indicates that an entity holds a specific role or function within a quest hub context.
-
E.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.