Triple
T31495608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Dawson Calvert |
E803530
|
entity |
| Predicate | sharesLifeboatNumber |
P65997
|
FINISHED |
| Object | Lifeboat 14 (nearby rescue context) |
—
|
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: Lifeboat 14 (nearby rescue context) | Statement: [Rose Dawson Calvert, sharesLifeboatNumber, Lifeboat 14 (nearby rescue context)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLifeboatNumber Context triple: [Rose Dawson Calvert, sharesLifeboatNumber, Lifeboat 14 (nearby rescue context)]
-
A.
sharesLifeboatWith
chosen
Indicates that two or more entities are occupying or using the same lifeboat together.
-
B.
hasLifeboats
Indicates that an entity is equipped with or possesses one or more lifeboats for emergency use.
-
C.
hasLifeboatType
Indicates that an entity is associated with or equipped with a specific type of lifeboat.
-
D.
lifeboatCapacity
Indicates the maximum number of people or load that a lifeboat is designed and certified to safely carry.
-
E.
lifeboatsLaunched
Indicates that lifeboats have been deployed or put into the water from a vessel or structure.
- 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_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: April 30, 2026, 9:41 p.m.