Triple
T1018627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Airspace System governance |
E21988
|
entity |
| Predicate | includesPolicyDomain |
P5037
|
FINISHED |
| Object | airspace design and restructuring |
—
|
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: airspace design and restructuring | Statement: [National Airspace System governance, includesPolicyDomain, airspace design and restructuring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPolicyDomain Context triple: [National Airspace System governance, includesPolicyDomain, airspace design and restructuring]
-
A.
policyDomain
Indicates the thematic or subject-matter area to which a given policy, rule, or regulatory action belongs.
-
B.
coversPolicyArea
chosen
Indicates that a policy, document, or initiative includes or addresses a particular policy area or topic within its scope.
-
C.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
D.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
E.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c6005081909d9e56114c532d14 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.