Triple
T29582128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Torrance about the hotel’s history |
E753615
|
entity |
| Predicate | storyPosition |
P37669
|
FINISHED |
| Object | earlyInNarrative |
—
|
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: earlyInNarrative | Statement: [Jack Torrance about the hotel’s history, storyPosition, earlyInNarrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyPosition Context triple: [Jack Torrance about the hotel’s history, storyPosition, earlyInNarrative]
-
A.
positionInStory
chosen
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
B.
storyNumber
Indicates the numerical identifier assigned to a specific story within a collection, sequence, or dataset.
-
C.
stageReached
Indicates that a process, task, or entity has arrived at or completed a specific stage or phase within a defined progression.
-
D.
storyStatus
Indicates the current state or phase of a story within its lifecycle (e.g., planned, in progress, completed, or archived).
-
E.
positionInFiction
Indicates that one entity holds a specific role, status, or placement within a fictional work or narrative.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 6:07 p.m.