Triple
T18692114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auster AOP |
E457024
|
entity |
| Predicate | notableVariant |
P4680
|
FINISHED |
| Object | Auster AOP.5 |
—
|
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: Auster AOP.5 | Statement: [Auster AOP, notableVariant, Auster AOP.5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Auster AOP.5 Context triple: [Auster AOP, notableVariant, Auster AOP.5]
-
A.
Auster AOP
chosen
The Auster AOP is a British World War II-era light observation and liaison aircraft used primarily for artillery spotting and reconnaissance duties.
-
B.
Bristol Brigand
The Bristol Brigand was a British twin-engine ground-attack and anti-shipping aircraft developed in the 1940s for the Royal Air Force.
-
C.
Avro Anson
The Avro Anson was a British twin‑engine, multi‑role aircraft widely used before and during World War II for maritime patrol, training, and transport duties.
-
D.
Bristol 138
The Bristol 138 was a British high-altitude research aircraft of the 1930s that set several world altitude records.
-
E.
Hawker P.1040
The Hawker P.1040 was a British prototype jet fighter design that led directly to the development of the Royal Navy’s Hawker Sea Hawk carrier-based aircraft.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e4756881909335e1e7b3c23e28 |
completed | April 19, 2026, 11:19 p.m. |
Created at: April 10, 2026, 11:49 a.m.