Triple
T28889343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Rose Dawson Calvert |
E732652
|
entity |
| Predicate | remembersEvent |
P165487
|
FINISHED |
| Object | being drawn by Jack Dawson |
—
|
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: being drawn by Jack Dawson | Statement: [Old Rose Dawson Calvert, remembersEvent, being drawn by Jack Dawson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remembersEvent Context triple: [Old Rose Dawson Calvert, remembersEvent, being drawn by Jack Dawson]
-
A.
recordEvent
Indicates that an entity logs or stores information about a specific occurrence or action as an event.
-
B.
rememberedFor
Indicates that one entity is known or recognized primarily because of, or in association with, another entity or achievement.
-
C.
revisitsEvent
Indicates that an entity returns to and attends or engages with an event again after having previously done so.
-
D.
rememberedThrough
Indicates that one entity is remembered, commemorated, or kept in memory by means of, or through the influence of, another entity or medium.
-
E.
isRememberedOn
Indicates that an entity is commemorated, recalled, or honored on a specific date or occasion.
- 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_69f65a744e1c8190bff56db4cb0b68df |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 7:53 a.m.