Triple
T2109214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Air Defense Forces |
E42465
|
entity |
| Predicate | hadUnitType |
P28425
|
FINISHED |
| Object | air defense armies |
—
|
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 defense armies | Statement: [Soviet Air Defense Forces, hadUnitType, air defense armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadUnitType Context triple: [Soviet Air Defense Forces, hadUnitType, air defense armies]
-
A.
hasSpecialUnit
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
-
B.
hasBasedUnit
Indicates that something is defined or measured in terms of a specified base unit.
-
C.
hostsUnitType
Indicates that one entity serves as a location or platform that accommodates or contains a specified type of unit.
-
D.
associatedUnitType
chosen
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
E.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae1bacc8190beffc9d0470e9190 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.