Triple
T24835213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KSAV |
E621450
|
entity |
| Predicate | isInFAADistrict |
P29284
|
FINISHED |
| Object | Atlanta Airports District Office |
—
|
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: Atlanta Airports District Office | Statement: [KSAV, isInFAADistrict, Atlanta Airports District Office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInFAADistrict Context triple: [KSAV, isInFAADistrict, Atlanta Airports District Office]
-
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.
isWithinMetroArea
Indicates that one location lies inside the geographic boundaries of a specified metropolitan area.
-
C.
isWithinFederalCapitalTerritory
Indicates that one entity is geographically located inside the boundaries of the federal capital territory of another governing body or jurisdiction.
-
D.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
E.
basedInDistrict
chosen
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:17 a.m.