Triple
T15463997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Ocean Tunnel |
E371977
|
entity |
| Predicate | isSubsea |
P13850
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Atlantic Ocean Tunnel, isSubsea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubsea Context triple: [Atlantic Ocean Tunnel, isSubsea, true]
-
A.
isSubseaBasinOf
Indicates that a geological basin is located beneath the sea and is part of, or contained within, a larger marine or oceanic region.
-
B.
submersibleName
Indicates that a submersible is identified by or associated with a specific name.
-
C.
submerged
chosen
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
D.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
E.
isShallowSea
Indicates that a body of water is a shallow marine area, typically near coasts or continental shelves, rather than deep ocean.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1927708190a0d2b63e75469a0e |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.