Triple
T6036449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PZL P.11 |
E134432
|
entity |
| Predicate | combatRole1939 |
P16542
|
FINISHED |
| Object | interceptor against German Luftwaffe |
—
|
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: interceptor against German Luftwaffe | Statement: [PZL P.11, combatRole1939, interceptor against German Luftwaffe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatRole1939 Context triple: [PZL P.11, combatRole1939, interceptor against German Luftwaffe]
-
A.
worldWarIIRole
chosen
Indicates the specific role, position, or function an entity had in relation to World War II.
-
B.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
C.
postWWIIRole
Indicates the role, position, or function an entity assumed or performed in the period following World War II.
-
D.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
E.
combatantRoleOfGermany
Indicates that the specified role is one that Germany held as a combatant in a particular conflict or war.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b4e3ec819089b2d119ea2953fe |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.