Triple
T30832201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Jacob Astor VI |
E785252
|
entity |
| Predicate | fatherDiedIn |
P170546
|
FINISHED |
| Object | sinking of the 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: sinking of the RMS Titanic | Statement: [John Jacob Astor VI, fatherDiedIn, sinking of the RMS Titanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fatherDiedIn Context triple: [John Jacob Astor VI, fatherDiedIn, sinking of the RMS Titanic]
-
A.
fatherDiedAt
Indicates that the specified person's father died at a particular time, place, or under certain circumstances.
-
B.
canonicalDeathOfFather
Indicates that the referenced death event is the officially recognized or primary recorded death of the subject’s father.
-
C.
fatherDateOfDeath
Indicates the date on which the subject's father died.
-
D.
fatherWas
Indicates that one entity was the male parent (father) of another entity in the past.
-
E.
grandfatherDiedAt
Indicates that a specified grandfather died at a particular time or in a particular place.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f690fa95848190bee45bbb1a756955 |
completed | May 3, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:44 p.m.