Triple
T6734551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin Airport |
E153719
|
entity |
| Predicate | operator |
P179
|
FINISHED |
| Object | daa plc |
E153362
|
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 plc | Statement: [Dublin Airport, operator, daa plc]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: daa plc Context triple: [Dublin Airport, operator, daa plc]
-
A.
daa
chosen
daa is the Irish state-owned airport operator responsible for managing Dublin Airport and other aviation and travel-related businesses.
-
B.
DAA
DAA is the IATA airport code for Davison Army Airfield, a U.S. Army aviation facility located at Fort Belvoir, Virginia.
-
C.
DDC
DDC is the IATA airport code for Dodge City Regional Airport, a public airport serving Dodge City in southwestern Kansas, United States.
-
D.
DDC
DDC is a widely used library classification system that organizes books and other materials into numbered subject categories for easy retrieval.
-
E.
DDC
DDC is the Dart Dev Compiler, a tool that compiles Dart code to efficient JavaScript for web development.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16ecbe08190b019d547f631a725 |
completed | March 27, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70b0703288190906cfcaba9d9c85a |
completed | March 27, 2026, 10:56 p.m. |
Created at: March 27, 2026, 2:09 p.m.