Triple
T8835962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Support Facility Thurmont |
E210266
|
entity |
| Predicate | hasRestrictedAirspace |
P4885
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Naval Support Facility Thurmont, hasRestrictedAirspace, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestrictedAirspace Context triple: [Naval Support Facility Thurmont, hasRestrictedAirspace, yes]
-
A.
hasAirspace
Indicates that one entity possesses, controls, or is associated with a defined region of airspace relative to another entity or area.
-
B.
appliesToAirspaceOf
chosen
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
C.
rangeAgainstAircraft
Indicates that one entity measures, determines, or engages the distance to an aircraft target.
-
D.
SVFRPermitted
Indicates that operating under Special Visual Flight Rules (SVFR) is allowed in the given airspace or conditions.
-
E.
hasRunwayAccessTo
Indicates that one location or facility is directly connected to another via a usable runway, allowing aircraft to move between them without leaving runway infrastructure.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6069ad7881909e31010e73e26f91 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.