Triple
T26305961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabwah Governorate |
E661681
|
entity |
| Predicate | traversedByPipeline |
P148928
|
FINISHED |
| Object | Yemen LNG 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: Yemen LNG pipeline | Statement: [Shabwah Governorate, traversedByPipeline, Yemen LNG pipeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversedByPipeline Context triple: [Shabwah Governorate, traversedByPipeline, Yemen LNG pipeline]
-
A.
crossedByPipeline
chosen
Indicates that a pipeline physically passes across or through the referenced entity or area.
-
B.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
C.
hasPipeline
Indicates that one entity possesses, contains, or is associated with a pipeline used to transport or process something.
-
D.
hasTrainingPipelineFrom
Indicates that something is produced or derived as the result of a specified training pipeline or process.
-
E.
transitionedThrough
Indicates that an entity passed from one state, phase, or condition to another by way of an intermediate state, phase, or condition.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 10:18 p.m.