Triple
T17574351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat CR.30 |
E428022
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Fiat CR.32 |
—
|
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: Fiat CR.32 | Statement: [Fiat CR.30, successor, Fiat CR.32]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fiat CR.32 Context triple: [Fiat CR.30, successor, Fiat CR.32]
-
A.
Fiat CR.32
chosen
The Fiat CR.32 was an Italian biplane fighter aircraft of the 1930s, widely exported and used in several conflicts including the Spanish Civil War.
-
B.
Fiat CR.20
The Fiat CR.20 was an Italian single-seat biplane fighter aircraft of the 1920s, widely used by the Regia Aeronautica and several foreign air forces.
-
C.
Fiat CR.42 Falco
The Fiat CR.42 Falco was an Italian single-seat biplane fighter aircraft of World War II, noted as one of the last operational biplane fighters used in front-line service.
-
D.
Fiat CR.40
The Fiat CR.40 was an Italian prototype biplane fighter aircraft developed in the early 1930s as part of Fiat’s CR series of combat aircraft.
-
E.
Fiat CR.30
The Fiat CR.30 was an Italian biplane fighter aircraft of the early 1930s, serving as an important transitional design in Regia Aeronautica service before more advanced models appeared.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4593403648190836266dbdb6cfc9f |
completed | April 19, 2026, 4:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.