Triple
T31495593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Dawson Calvert |
E803530
|
entity |
| Predicate | adoptsSurnameFrom |
P122667
|
FINISHED |
| Object | Jack Dawson |
—
|
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: Jack Dawson | Statement: [Rose Dawson Calvert, adoptsSurnameFrom, Jack Dawson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptsSurnameFrom Context triple: [Rose Dawson Calvert, adoptsSurnameFrom, Jack Dawson]
-
A.
laterTakesSurnameFrom
chosen
Indicates that one entity adopts or assumes the surname of another entity at a later point in time.
-
B.
adoptedFamilyName
Indicates that an entity has taken or been given a family name different from their original one, typically through adoption, marriage, or personal choice.
-
C.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
D.
droppedSurname
Indicates that an entity has ceased using a previously held surname, typically by omitting or removing it from their current full name.
-
E.
adoptedFrom
Indicates that an entity has been taken into guardianship, ownership, or use from another source or origin.
- 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_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 30, 2026, 9:41 p.m.