Triple
T8157117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manderley |
E190476
|
entity |
| Predicate | fateInStory |
P24728
|
FINISHED |
| Object | destroyed by fire |
—
|
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: destroyed by fire | Statement: [Manderley, fateInStory, destroyed by fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateInStory Context triple: [Manderley, fateInStory, destroyed by fire]
-
A.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
eventualFate
chosen
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
C.
knowledgeOfFate
Indicates that one entity is aware of or understands the destined or predetermined outcome concerning another entity or event.
-
D.
fateLocation
Indicates the location where an entity ultimately ends up or meets its final outcome.
-
E.
ascentStageFate
Indicates the outcome or final status of an ascent stage after it has completed its primary mission or operation.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44da14a481909f8d3277762b0e75 |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.