Triple
T27092080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Numaligarh Refinery Limited |
E686192
|
entity |
| Predicate | hasPipelineProject |
P14971
|
FINISHED |
| Object | Numaligarh–Silghat crude oil 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: Numaligarh–Silghat crude oil pipeline | Statement: [Numaligarh Refinery Limited, hasPipelineProject, Numaligarh–Silghat crude oil pipeline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPipelineProject Context triple: [Numaligarh Refinery Limited, hasPipelineProject, Numaligarh–Silghat crude oil pipeline]
-
A.
hasPipeline
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.
hasPipelineTerminal
Indicates that one entity possesses, contains, or is associated with a pipeline terminal as part of its infrastructure or connections.
-
D.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
E.
hasProject
chosen
Indicates that an entity is associated with or responsible for a particular project.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.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 27, 2026, 8:41 a.m.