Triple
T37897233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Niuzao Temple |
E945312
|
entity |
| Predicate | questIntegration |
P183780
|
FINISHED |
| Object | linked to Townlong Steppes questlines |
—
|
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: linked to Townlong Steppes questlines | Statement: [Siege of Niuzao Temple, questIntegration, linked to Townlong Steppes questlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questIntegration Context triple: [Siege of Niuzao Temple, questIntegration, linked to Townlong Steppes questlines]
-
A.
questHubFor
Indicates a relationship where one entity serves as the central location or main coordination point for quests associated with another entity.
-
B.
questHubNPC
Indicates that an NPC serves as a central provider or coordinator of quests for players.
-
C.
questlineFeature
chosen
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
D.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
-
E.
questLocationFor
Indicates that a particular location is the place where a given quest occurs, is based, or must be undertaken.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:19 p.m.