Triple
T28605571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gunslinger |
E724035
|
entity |
| Predicate | introducesQuest |
P101767
|
FINISHED |
| Object | Roland Deschain’s journey to the Dark Tower |
—
|
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: Roland Deschain’s journey to the Dark Tower | Statement: [The Gunslinger, introducesQuest, Roland Deschain’s journey to the Dark Tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesQuest Context triple: [The Gunslinger, introducesQuest, Roland Deschain’s journey to the Dark Tower]
-
A.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
-
B.
addsQuest
chosen
Indicates that one entity assigns or introduces a quest to another entity or into a system.
-
C.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
D.
objectOfQuest
Indicates that one entity is the target, goal, or item being sought or pursued in another entity’s quest or mission.
-
E.
questedBy
Indicates that a quest or mission is initiated, assigned, or undertaken by a particular entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 4:27 a.m.