Triple
T8240075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gas Act 1972 |
E192511
|
entity |
| Predicate | industryTypeRegulated |
P34837
|
FINISHED |
| Object | natural gas |
—
|
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: natural gas | Statement: [Gas Act 1972, industryTypeRegulated, natural gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryTypeRegulated Context triple: [Gas Act 1972, industryTypeRegulated, natural gas]
-
A.
industryRegime
Indicates a regulatory or governance framework that controls or shapes how an industry operates.
-
B.
governmentTypeRegulated
Indicates that the type or form of government of an entity is subject to regulation, control, or definition by another authority or governing framework.
-
C.
typeOfAgencyRegulated
Indicates that one entity is the kind or category of agency that is subject to regulation by another entity.
-
D.
regulatedIn
Indicates that one entity’s activity, expression, or occurrence is controlled, influenced, or modulated by another entity within a specific context or system.
-
E.
subjectToRegulation
chosen
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb783cce5c8190bf116704d2923ade |
completed | March 31, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:47 p.m.