Triple
T35420228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukhoi P-1 |
E1023762
|
entity |
| Predicate | airForceContext |
P23972
|
FINISHED |
| Object | Soviet air defense modernization |
—
|
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: Soviet air defense modernization | Statement: [Sukhoi P-1, airForceContext, Soviet air defense modernization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airForceContext Context triple: [Sukhoi P-1, airForceContext, Soviet air defense modernization]
-
A.
airForceUser
Indicates that an entity is a member of, affiliated with, or acting on behalf of an air force organization.
-
B.
airForceCommand
Indicates a command relationship in which one entity exercises authority over the operations, organization, or administration of an air force or air force unit.
-
C.
airCommander
Indicates that an entity serves as the commanding officer or leader of air forces or air operations for another entity.
-
D.
airForceInvolved
chosen
Indicates that an air force participates in, contributes to, or is otherwise involved in a specified event, operation, or situation.
-
E.
airForceVariant
Indicates that one entity is a version or model of something specifically adapted for use by an air force.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7958b1e2481909227813f382e79a0 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.