Triple
T32288304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transbaikal Military District |
E824893
|
entity |
| Predicate | secondaryForces |
P101520
|
FINISHED |
| Object | tactical aviation |
—
|
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: tactical aviation | Statement: [Transbaikal Military District, secondaryForces, tactical aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryForces Context triple: [Transbaikal Military District, secondaryForces, tactical aviation]
-
A.
hasSecondaryForces
chosen
Indicates that an entity is subject to or associated with additional, indirect, or supporting forces beyond its primary forces.
-
B.
primaryForces
Indicates a relationship where one or more forces are identified as the main or dominant contributors to an effect, behavior, or outcome among all forces involved.
-
C.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
thirdForce
Indicates that an additional, distinct force is acting on an entity beyond the primary two forces already considered.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 1, 2026, 12:44 a.m.