Triple
T31495591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Dawson Calvert |
E803530
|
entity |
| Predicate | revealsPastAs |
P120028
|
FINISHED |
| Object | Rose DeWitt Bukater |
—
|
NE NERFINISHED |
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: Rose DeWitt Bukater | Statement: [Rose Dawson Calvert, revealsPastAs, Rose DeWitt Bukater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealsPastAs Context triple: [Rose Dawson Calvert, revealsPastAs, Rose DeWitt Bukater]
-
A.
revealsPastIdentityTo
Indicates that one entity discloses or makes known another entity’s former or previously hidden identity to someone.
-
B.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
-
C.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
-
D.
hasMysteriousPast
Indicates that an entity possesses a past that is unknown, hidden, or only partially revealed, often implying secrets or unexplained events.
-
E.
unveiledAs
chosen
Indicates that one entity is revealed, presented, or disclosed in the role, identity, or form of another entity.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:41 p.m.