Triple
T36254727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Riband |
E891901
|
entity |
| Predicate | lastHeldBy |
P3710
|
FINISHED |
| Object | SS United States |
—
|
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: SS United States | Statement: [Blue Riband, lastHeldBy, SS United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastHeldBy Context triple: [Blue Riband, lastHeldBy, SS United States]
-
A.
lastHeldIn
Indicates that an event or state most recently took place or was hosted in a particular location or context.
-
B.
laterHeldBy
Indicates that an entity was possessed, controlled, or owned by another entity at a subsequent time after an earlier state or holder.
-
C.
hasBeenHeldBy
Indicates that an entity has previously possessed, controlled, or occupied another entity for some duration in the past.
-
D.
lastHolder
chosen
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
E.
hasHeldBy
Indicates that one entity has been physically or conceptually grasped, possessed, or kept in the control 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5fd3f8481908b9380f82a2310f0 |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.