Triple
T37836572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Caucasus Pipeline |
E943353
|
entity |
| Predicate | followsRouteSimilarTo |
P130931
|
FINISHED |
| Object | Baku–Tbilisi–Ceyhan pipeline |
—
|
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: Baku–Tbilisi–Ceyhan pipeline | Statement: [South Caucasus Pipeline, followsRouteSimilarTo, Baku–Tbilisi–Ceyhan pipeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRouteSimilarTo Context triple: [South Caucasus Pipeline, followsRouteSimilarTo, Baku–Tbilisi–Ceyhan pipeline]
-
A.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
B.
isRelatedRouteOf
chosen
Indicates that one route is connected to, associated with, or serves as an alternative or complementary path to another route.
-
C.
followsRouteShape
Indicates that an entity travels or operates along a predefined path or geometric route pattern.
-
D.
servesAsRouteTo
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
E.
usesFormerRouteOf
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: May 3, 2026, 4:19 p.m.