Triple
T36914745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAA |
E913013
|
entity |
| Predicate | notableRegulatoryOutcome |
—
|
GENERATED |
| Object | break-up of UK airport ownership concentration |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRegulatoryOutcome Context triple: [BAA, notableRegulatoryOutcome, break-up of UK airport ownership concentration]
-
A.
regulatoryOutcome
chosen
Indicates the result or consequence of a regulatory process, such as approval, rejection, modification, or other formal decision made by a regulatory authority regarding an entity or action.
-
B.
notableRegulatoryEvent
Indicates a significant regulatory action, decision, or change that has materially affected or is closely associated with the subject entity.
-
C.
regulatoryOutput
Indicates that one entity produces or issues a rule, standard, or directive that governs or constrains the behavior of another entity or process.
-
D.
regulationImpact
Indicates how a regulation influences, constrains, or alters the behavior, performance, or outcomes associated with the related entities.
-
E.
notableRule
Indicates that a rule or regulation is particularly significant, prominent, or noteworthy within a given context.
- F. None of above.
Provenance (1 batch)
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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.