Triple
T28138893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Gas Corporation |
E714286
|
entity |
| Predicate | operatedPipelines |
P141870
|
FINISHED |
| Object | national gas transmission system |
—
|
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: national gas transmission system | Statement: [British Gas Corporation, operatedPipelines, national gas transmission system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedPipelines Context triple: [British Gas Corporation, operatedPipelines, national gas transmission system]
-
A.
operatedPipelinesIn
chosen
Indicates that an entity has operated or managed pipelines within a specified location or jurisdiction.
-
B.
hasPetrochemicalPipelines
Indicates that one entity possesses, controls, or is associated with petrochemical pipelines connecting it to other locations or facilities.
-
C.
operatedCanal
Indicates that one entity managed and ran the functioning of a canal for another entity or in a given context.
-
D.
typeOfCanalOperated
Indicates that one entity operates or manages a canal of the specified type.
-
E.
operatedFacilitiesIn
Indicates that an entity has managed or run facilities located within a specified place or jurisdiction.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 27, 2026, 9:52 p.m.