Triple
T3183126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davison Army Airfield |
E66636
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | DAA |
E333633
|
NE 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: DAA | Statement: [Davison Army Airfield, FAAcode, DAA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DAA Context triple: [Davison Army Airfield, FAAcode, DAA]
-
A.
DAA
chosen
DAA is the IATA airport code for Davison Army Airfield, a U.S. Army aviation facility located at Fort Belvoir, Virginia.
-
B.
daa
daa is the Irish state-owned airport operator responsible for managing Dublin Airport and other aviation and travel-related businesses.
-
C.
DDA
DDA is the commonly used abbreviation for the Division on Dynamical Astronomy, a professional group focused on the study of celestial dynamics within the American Astronomical Society.
-
D.
DSA
DSA (Digital Signature Algorithm) is a widely used public-key cryptographic standard designed for creating and verifying digital signatures to ensure data integrity and authentication.
-
E.
DA
DA is the official abbreviation for the United States Department of the Army, the federal agency responsible for organizing, training, and equipping the U.S. Army.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6bea1788190bbce7cb52f8e72e8 |
completed | March 8, 2026, 4:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b24b777fe881909764e2f2cdb68479 |
completed | March 12, 2026, 5:13 a.m. |
Created at: March 8, 2026, 3:06 p.m.