Triple
T2229342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class A airspace |
E48727
|
entity |
| Predicate | ATCServiceRequired |
P4885
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Class A airspace, ATCServiceRequired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ATCServiceRequired Context triple: [Class A airspace, ATCServiceRequired, true]
-
A.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
B.
hasATCCode
Indicates that a pharmaceutical product or substance is assigned a specific Anatomical Therapeutic Chemical (ATC) classification code.
-
C.
serviceCommitmentRequired
Indicates that entering into or receiving something involves an obligation to perform a specified period or type of service.
-
D.
appliesToAirspaceOf
chosen
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
E.
typicalServiceRequirement
Indicates that a certain condition, resource, or specification is normally needed or expected for a service to be properly provided or operated.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0685b688190857a76c1043f4b92 |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.