Triple
T8252388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Signals Directorate |
E192987
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | ASD |
E192987
|
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: ASD | Statement: [Australian Signals Directorate, abbreviation, ASD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ASD Context triple: [Australian Signals Directorate, abbreviation, ASD]
-
A.
ASD
chosen
ASD is the Australian Signals Directorate, Australia’s national authority for signals intelligence, cyber security, and offensive cyber operations.
-
B.
ASD
ASD is the official railway station code used to identify Amsterdam Centraal station in the Netherlands.
-
C.
ASD
ASD is the IATA airport code for Andros Town International Airport, a public airport serving Andros Island in the Bahamas.
-
D.
ASDZ
ASDZ is the station code used to identify Amsterdam Zuid railway station in the Netherlands.
-
E.
ASDPPP
ASDPPP is a comprehensive book by Robert C. Martin that explores agile software development through core principles, design patterns, and best practices for building maintainable code.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78ca4b0881909bb1fb550dba59e7 |
completed | March 31, 2026, 7:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd3540a0988190b8e48988279403db |
completed | April 1, 2026, 3:09 p.m. |
Created at: March 30, 2026, 5:48 p.m.