Triple
T37499959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franz Schieß |
E931928
|
entity |
| Predicate | numberOfAerialVictoriesOnWesternFront |
P12250
|
FINISHED |
| Object | 12 |
—
|
LITERAL 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: 12 | Statement: [Franz Schieß, numberOfAerialVictoriesOnWesternFront, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAerialVictoriesOnWesternFront Context triple: [Franz Schieß, numberOfAerialVictoriesOnWesternFront, 12]
-
A.
numberOfAerialVictories
chosen
Indicates the count of successful aerial combat victories achieved by an entity over opposing aircraft.
-
B.
estimatedAerialVictories
Indicates an approximate count of aerial combat victories attributed to an entity, rather than an exact, confirmed total.
-
C.
airSuperiorityAchievedBy
Indicates that one entity has gained dominant control of the airspace over another entity or area, typically through superior air power or air defense capabilities.
-
D.
typeOfAerialVictories
Indicates the specific category or classification of aerial victories associated with an entity.
-
E.
battleHonoursCount
Indicates the number of battle honours associated with an entity, such as a military unit, ship, or individual.
- F. None of above.
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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.