Triple
T37554778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Barrens |
E933668
|
entity |
| Predicate | notableQuestHub |
P100057
|
FINISHED |
| Object | Crossroads |
E937791
|
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: Crossroads | Statement: [The Barrens, notableQuestHub, Crossroads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableQuestHub Context triple: [The Barrens, notableQuestHub, Crossroads]
-
A.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
B.
zoneQuestHub
chosen
Indicates a relationship where a particular zone serves as the central hub or main base for quests within a game or system.
-
C.
notableDungeon
Indicates that an entity is recognized as a significant or noteworthy dungeon, typically due to its importance, uniqueness, or prominence.
-
D.
questlineFeature
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
E.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
- 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_69f76eca55bc8190acf25741793d5dac |
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_6a40a7ee13ac81909d349572569d1864 |
completed | June 28, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.