Triple
T32686353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinz-Wolfgang Schnaufer |
E835736
|
entity |
| Predicate | victoriesAgainst |
P34090
|
FINISHED |
| Object | RAF Bomber Command aircraft |
—
|
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: RAF Bomber Command aircraft | Statement: [Heinz-Wolfgang Schnaufer, victoriesAgainst, RAF Bomber Command aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victoriesAgainst Context triple: [Heinz-Wolfgang Schnaufer, victoriesAgainst, RAF Bomber Command aircraft]
-
A.
wonAgainst
chosen
Indicates that one entity achieved victory over another in a competition, conflict, or contest.
-
B.
numberOfOpponentsBeaten
Indicates the count of distinct opponents that an entity has successfully defeated.
-
C.
serviceNumberOfVictories
Indicates the number of victories achieved in the context of a particular service or service-related activity.
-
D.
numberOfWins
Indicates the count of times an entity has achieved victory in a relevant context or competition.
-
E.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c81665688190bc0cde92cf4d619f |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.