Triple
T26893680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oil India Limited |
E677844
|
entity |
| Predicate | hasPipelineNetwork |
P129093
|
FINISHED |
| Object | crude oil pipelines in Northeast India |
—
|
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: crude oil pipelines in Northeast India | Statement: [Oil India Limited, hasPipelineNetwork, crude oil pipelines in Northeast India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPipelineNetwork Context triple: [Oil India Limited, hasPipelineNetwork, crude oil pipelines in Northeast India]
-
A.
hasPipeline
chosen
Indicates that one entity possesses, contains, or is associated with a pipeline used to transport or process something.
-
B.
hasPipelineConnection
Indicates that one entity is linked to another via a pipeline through which materials, fluids, or data can flow.
-
C.
hasPipes
Indicates that one entity is equipped with, contains, or is connected to one or more pipes.
-
D.
operatedPipelinesIn
Indicates that an entity has operated or managed pipelines within a specified location or jurisdiction.
-
E.
hasNetworkStructure
Indicates that one entity possesses, exhibits, or is organized according to a particular network-based structure defined by another entity or specification.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 5:46 a.m.