Triple
T31495577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Dawson Calvert |
E803530
|
entity |
| Predicate | classOnShip |
P172867
|
FINISHED |
| Object | first class (as Rose DeWitt Bukater) |
—
|
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: first class (as Rose DeWitt Bukater) | Statement: [Rose Dawson Calvert, classOnShip, first class (as Rose DeWitt Bukater)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classOnShip Context triple: [Rose Dawson Calvert, classOnShip, first class (as Rose DeWitt Bukater)]
-
A.
hasShipInClass
Indicates that an entity possesses or includes at least one ship that belongs to a specified ship class.
-
B.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
C.
supportsClassOfShip
Indicates that one entity is capable of accommodating, servicing, or otherwise functionally supporting a specified class of ship.
-
D.
usedOnShipClass
Indicates that something (such as equipment, technology, or a system) is employed or installed on a particular class of ship.
-
E.
componentShip
Indicates that one entity is a physical or logical component or part of another entity, such that the whole is composed of or depends on that component.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 9:41 p.m.