Triple
T18497589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tranquility |
E451987
|
entity |
| Predicate | hasDockingOrBerthingPort |
P14981
|
FINISHED |
| Object | Common Berthing Mechanism ports |
—
|
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: Common Berthing Mechanism ports | Statement: [Tranquility, hasDockingOrBerthingPort, Common Berthing Mechanism ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDockingOrBerthingPort Context triple: [Tranquility, hasDockingOrBerthingPort, Common Berthing Mechanism ports]
-
A.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
-
B.
hasBerths
Indicates that one entity provides or contains sleeping or docking berths for another entity.
-
C.
isMainDeepWaterPortFor
Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
-
D.
berthingSystem
chosen
Indicates a system or mechanism used to dock, moor, or secure one vehicle, vessel, or structure to another.
-
E.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c15dec8190941e7c7a4cdebb66 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.