Triple
T27934705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Squadron |
E708071
|
entity |
| Predicate | tacticalSpecialty |
P50132
|
FINISHED |
| Object | trench run attack |
—
|
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: trench run attack | Statement: [Red Squadron, tacticalSpecialty, trench run attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticalSpecialty Context triple: [Red Squadron, tacticalSpecialty, trench run attack]
-
A.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
B.
tacticalPurpose
Indicates the specific tactical objective or intended operational role that an action, asset, or decision is meant to achieve within a broader plan or mission.
-
C.
tacticalFeatureUsed
Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
-
D.
tacticalStyle
chosen
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
E.
tacticalOfficer
Indicates that an entity serves in the role or capacity of a tactical officer in relation to another entity or organization.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 7:04 p.m.