Triple
T1388297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 302 Polish Fighter Squadron |
E29895
|
entity |
| Predicate | operationalStatusDuringWWII |
P19660
|
FINISHED |
| Object | active combat unit |
—
|
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: active combat unit | Statement: [No. 302 Polish Fighter Squadron, operationalStatusDuringWWII, active combat unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStatusDuringWWII Context triple: [No. 302 Polish Fighter Squadron, operationalStatusDuringWWII, active combat unit]
-
A.
statusDuringWorldWarII
chosen
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
B.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
C.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
D.
statusDuring1939Campaign
Indicates the role, condition, or state an entity held specifically during the 1939 military campaign.
-
E.
WWIIUse
Indicates that one entity made use of another entity during World War II, typically for military, strategic, or wartime-related purposes.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c35ad578819090abf96222112bda |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.