Triple
T28889399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of the Ocean necklace |
E732654
|
entity |
| Predicate | settingOfFinalFate |
P175997
|
FINISHED |
| Object | above wreck of RMS Titanic |
—
|
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: above wreck of RMS Titanic | Statement: [Heart of the Ocean necklace, settingOfFinalFate, above wreck of RMS Titanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfFinalFate Context triple: [Heart of the Ocean necklace, settingOfFinalFate, above wreck of RMS Titanic]
-
A.
settingOfDeath
Indicates the specific place or environment in which an entity’s death occurred.
-
B.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
C.
chosenFate
Indicates that an entity has actively selected or accepted a particular destiny or outcome, rather than having it imposed by external forces.
-
D.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
E.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 28, 2026, 7:53 a.m.