Triple
T13388121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A 32A Lansen |
E319497
|
entity |
| Predicate | airForceDesignation |
P7137
|
FINISHED |
| Object | A 32A |
E319497
|
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: A 32A | Statement: [A 32A Lansen, airForceDesignation, A 32A]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A 32A Context triple: [A 32A Lansen, airForceDesignation, A 32A]
-
A.
A32
A32 is an Australian state highway route designation assigned to the Mitchell Highway and associated connecting roads.
-
B.
A232
The A232 is a major road in the London Borough of Bromley that provides an important route for local and through traffic across South London.
-
C.
A-23
A-23 is the internal station code assigned to Warsaw's Młociny metro station on Line M1.
-
D.
3A
3A is a highway designation used for several auxiliary or alternate routes of U.S. Route 3 and related highways in New England.
-
E.
A 32A Lansen
chosen
The A 32A Lansen was the ground-attack version of Sweden’s Saab 32 Lansen jet aircraft, optimized for strike missions with enhanced weapons and attack systems.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d3a40081909ba49556130ad0e7 |
completed | April 12, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f72691c8d08190b971d7e914863cc1 |
completed | May 3, 2026, 10:42 a.m. |
Created at: April 9, 2026, 9:34 p.m.