Triple
T6036420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PZL P.11 |
E134432
|
entity |
| Predicate | roleAtWarStart |
P1549
|
FINISHED |
| Object | primary frontline fighter of Poland |
—
|
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: primary frontline fighter of Poland | Statement: [PZL P.11, roleAtWarStart, primary frontline fighter of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtWarStart Context triple: [PZL P.11, roleAtWarStart, primary frontline fighter of Poland]
-
A.
roleChangeLaterWar
Indicates that an entity’s role or position changes at a later stage within the context of a war or armed conflict.
-
B.
roleAfterWar
Indicates the role or position an entity assumes following the end of a war or armed conflict.
-
C.
roleDuringConquest
Indicates the specific function, position, or capacity an entity held in relation to a particular conquest event.
-
D.
associatedWithWar
chosen
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
-
E.
roleDuringColdWar
Indicates the specific position, function, or involvement an entity had in the context of the Cold War period.
- 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.