Triple
T15422151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Immelmann |
E369406
|
entity |
| Predicate | airVictories |
P12250
|
FINISHED |
| Object | over 10 confirmed victories |
—
|
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: over 10 confirmed victories | Statement: [Max Immelmann, airVictories, over 10 confirmed victories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airVictories Context triple: [Max Immelmann, airVictories, over 10 confirmed victories]
-
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.
aircraftLosses
Indicates the number or occurrence of aircraft that have been destroyed, damaged beyond repair, or otherwise lost.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ebe7b1081908e6b9e6e128a8d5d |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.