Triple
T21958867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi A7M Reppū |
E542266
|
entity |
| Predicate | JapaneseDesignation |
P133352
|
FINISHED |
| Object | A7M |
—
|
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: A7M | Statement: [Mitsubishi A7M Reppū, JapaneseDesignation, A7M]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A7M Context triple: [Mitsubishi A7M Reppū, JapaneseDesignation, A7M]
-
A.
A7M
chosen
The A7M was a Japanese World War II carrier-based fighter aircraft developed by Mitsubishi as the intended successor to the famous A6M Zero.
-
B.
A7
A7 is the two-character IATA airline designator assigned to Calafia Airlines, a regional carrier based in Mexico.
-
C.
A7
A7 is a designated Australian state highway route number associated with the Gregory Highway in Queensland.
-
D.
A7
A7 is a major European motorway designation used for key north–south and east–west highway routes in several countries.
-
E.
A70
The A70 is a major road in Scotland that connects Edinburgh with Ayr, passing through several towns and rural areas along its route.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1244204f081909742d4fe138610d6 |
completed | April 28, 2026, 9:18 p.m. |
Created at: April 16, 2026, 8 p.m.