Triple
T26906210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Star Line |
E677261
|
entity |
| Predicate | operatedOnOcean |
P84216
|
FINISHED |
| Object | Atlantic Ocean |
—
|
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: Atlantic Ocean | Statement: [Red Star Line, operatedOnOcean, Atlantic Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedOnOcean Context triple: [Red Star Line, operatedOnOcean, Atlantic Ocean]
-
A.
navigatedOcean
Indicates that an entity traveled or steered a vessel across or through an ocean.
-
B.
operatedOnWaterBody
chosen
Indicates that an entity performs its operation or activity on or in a specific body of water.
-
C.
hasOcean
Indicates that a geographic region, country, or landmass is bordered by or directly adjacent to a particular ocean.
-
D.
hasOceanInteraction
Indicates that an entity engages in or is subject to interactions, processes, or exchanges involving the ocean.
-
E.
hasOceanType
Indicates that a body of water is classified as belonging to a particular type of ocean or oceanic category.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 27, 2026, 5:59 a.m.