Triple
T35364484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDAV |
E1021590
|
entity |
| Predicate | isInAviationAuthorityRegion |
P183060
|
FINISHED |
| Object | EASA |
—
|
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: EASA | Statement: [EDAV, isInAviationAuthorityRegion, EASA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInAviationAuthorityRegion Context triple: [EDAV, isInAviationAuthorityRegion, EASA]
-
A.
isInFAARegion
Indicates that one entity (typically a location, airspace, or facility) lies within the jurisdictional area or region defined by the FAA (Federal Aviation Administration).
-
B.
isInAirspaceRegion
Indicates that an entity is located within or passing through a specified airspace region.
-
C.
isInNationalAirspaceSystem
Indicates that an aircraft, flight, or operation is currently within the boundaries and regulatory scope of a country's National Airspace System.
-
D.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
E.
hasIcaoRegion
Indicates that an entity is associated with a specific ICAO (International Civil Aviation Organization) region.
- F. None of above. chosen
Provenance (4 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.