Triple
T37787646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baku–Tbilisi–Ceyhan pipeline |
E941995
|
entity |
| Predicate | seaTerminal |
P189218
|
FINISHED |
| Object | Mediterranean Sea |
—
|
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: Mediterranean Sea | Statement: [Baku–Tbilisi–Ceyhan pipeline, seaTerminal, Mediterranean Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaTerminal Context triple: [Baku–Tbilisi–Ceyhan pipeline, seaTerminal, Mediterranean Sea]
-
A.
isDeepwaterPortTerminus
Indicates that a location serves as the endpoint or final stop of a transportation route at a deepwater port capable of accommodating large, ocean-going vessels.
-
B.
harbourSide
Indicates a location or object that is situated alongside or directly adjacent to a harbour.
-
C.
eraOfMajorUseAsFerryTerminal
Indicates the time period during which a location was primarily used as a ferry terminal.
-
D.
maritimeGatewayFor
Indicates a relationship where one location serves as the primary seaport or ocean-access point enabling maritime connectivity and trade for another location.
-
E.
stateOfHarbor
Indicates the current operational or physical condition or status of a harbor.
- F. None of above. chosen
Provenance (4 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbb9e69b7481909beaf8264d87c5e5 |
completed | May 6, 2026, 10 p.m. |
Created at: May 3, 2026, 4:19 p.m.