Triple
T17548182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doncaster Sheffield Airport |
E427384
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | DSA |
—
|
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: DSA | Statement: [Doncaster Sheffield Airport, IATAcode, DSA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DSA Context triple: [Doncaster Sheffield Airport, IATAcode, DSA]
-
A.
DSA
DSA is India’s tri-service Defence Space Agency responsible for coordinating and enhancing the country’s military space capabilities.
-
B.
DSA
chosen
DSA is the three-letter IATA airport code for Doncaster Sheffield Airport in South Yorkshire, England.
-
C.
DSA
DSA is the IATA airport code assigned to Dhusamareb Airport in Somalia.
-
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.
DAA
DAA is the IATA airport code for Davison Army Airfield, a U.S. Army aviation facility located at Fort Belvoir, Virginia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e454631e148190a1d46a6ecb79c71a |
completed | April 19, 2026, 4:04 a.m. |
Created at: April 10, 2026, 5:49 a.m.