Triple
T31389298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thneed factory |
E800685
|
entity |
| Predicate | statusByStoryEnd |
P106839
|
FINISHED |
| Object | abandoned |
—
|
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: abandoned | Statement: [Thneed factory, statusByStoryEnd, abandoned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusByStoryEnd Context triple: [Thneed factory, statusByStoryEnd, abandoned]
-
A.
storyStatus
Indicates the current state or phase of a story within its lifecycle (e.g., planned, in progress, completed, or archived).
-
B.
statusBySeriesEnd
Indicates the condition or outcome of an entity as it stands at the conclusion of a particular series.
-
C.
statusAtEndOfNovel
chosen
Indicates the final state or condition of an entity as it stands at the conclusion of the novel.
-
D.
narrativeStatus
Indicates the role or state of an element within a narrative, such as whether it is current, hypothetical, background, or otherwise positioned in the story’s progression.
-
E.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 29, 2026, 9:19 p.m.