Triple
T30946875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dark Tower (novel) |
E788416
|
entity |
| Predicate | linkedWorks |
P192714
|
FINISHED |
| Object | The Stand |
—
|
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 Stand | Statement: [The Dark Tower (novel), linkedWorks, The Stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedWorks Context triple: [The Dark Tower (novel), linkedWorks, The Stand]
-
A.
linkedRight
Indicates that one entity is directly connected or positioned to the right of another entity in a sequence or structure.
-
B.
linkedSupport
Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
-
C.
relatedWorkByAttribution
Indicates that one work is connected to another through explicit attribution, such as citation, acknowledgment, or credit given by the creator or source.
-
D.
linksJunction
Indicates that one element serves as a connecting junction between two or more other elements, establishing a link or intersection among them.
-
E.
linkedDocument
Indicates that one document is associated with or references another document in a meaningful way.
- F. None of above. chosen
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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.