Triple
T1388277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 302 Polish Fighter Squadron |
E29895
|
entity |
| Predicate | distinguishedIn |
P24496
|
FINISHED |
| Object | air combat |
—
|
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: air combat | Statement: [No. 302 Polish Fighter Squadron, distinguishedIn, air combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinguishedIn Context triple: [No. 302 Polish Fighter Squadron, distinguishedIn, air combat]
-
A.
hasDistinction
Indicates that one entity possesses, is awarded, or is recognized with a special honor, title, or mark of excellence in relation to another entity or context.
-
B.
isDistinguishedBy
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
C.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
D.
wasProminentIn
chosen
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
E.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
- 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.