Triple
T38465571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobh |
E912555
|
entity |
| Predicate | wasLastPortOfCallFor |
P47889
|
FINISHED |
| Object | RMS Titanic |
—
|
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: RMS Titanic | Statement: [Cobh, wasLastPortOfCallFor, RMS Titanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLastPortOfCallFor Context triple: [Cobh, wasLastPortOfCallFor, RMS Titanic]
-
A.
previousPortOfCall
Indicates that a specified location was the last port where a vessel stopped or was registered before its current position or status.
-
B.
isPortOfCallFor
Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
-
C.
departurePortOnFinalVoyage
Indicates the port from which an entity (such as a vessel) last departed on its final recorded voyage.
-
D.
lastEuropeanPortOfCall
chosen
Indicates the final European port at which a vessel or traveler stopped before departing for a non-European destination.
-
E.
isHomePortOf
Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.