Triple
T22734705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAR Brașov |
E562233
|
entity |
| Predicate | designed |
P184
|
FINISHED |
| Object | IAR 37 |
—
|
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: IAR 37 | Statement: [IAR Brașov, designed, IAR 37]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IAR 37 Context triple: [IAR Brașov, designed, IAR 37]
-
A.
IAR 38
The IAR 38 was a Romanian reconnaissance and light bomber aircraft developed in the late 1930s by Industria Aeronautică Română for use by the Royal Romanian Air Force.
-
B.
IAR 39
The IAR 39 was a Romanian World War II-era reconnaissance and light bomber aircraft produced by Industria Aeronautică Română (IAR).
-
C.
IAR 37 reconnaissance and light bomber aircraft
chosen
The IAR 37 was a Romanian World War II-era biplane used primarily for reconnaissance and light bombing missions.
-
D.
IAR 47
The IAR 47 was a Romanian World War II reconnaissance and light bomber aircraft developed by Industria Aeronautică Română (IAR).
-
E.
IAR 80 fighter aircraft
The IAR 80 was a Romanian World War II-era single-engine fighter and ground-attack aircraft, considered one of the most advanced domestically produced fighters in Eastern Europe at the time.
- 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1796f030881908e141564d442bd1b |
completed | April 29, 2026, 3:22 a.m. |
Created at: April 17, 2026, 3:22 p.m.