Triple
T35013167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangkorai |
E1009984
|
entity |
| Predicate | hasQuestHub |
P100057
|
FINISHED |
| Object | Evermore |
—
|
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: Evermore | Statement: [Bangkorai, hasQuestHub, Evermore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuestHub Context triple: [Bangkorai, hasQuestHub, Evermore]
-
A.
hasQuestHubRole
Indicates that an entity holds a specific role or function within a quest hub context.
-
B.
hasQuestContentIn
Indicates that a quest’s narrative or objectives are contained within or associated with a particular location, context, or container.
-
C.
hasQuestElement
Indicates that something is a component, step, or requirement that forms part of a larger quest or mission.
-
D.
questlineAvailableIn
Indicates that a particular questline can be accessed or played within a specified game, mode, or context.
-
E.
zoneQuestHub
chosen
Indicates a relationship where a particular zone serves as the central hub or main base for quests within a game or system.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.