Triple
T10051662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Walker |
E207761
|
entity |
| Predicate | hasTrainingCapability |
P24513
|
FINISHED |
| Object | brigade-level exercises |
—
|
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: brigade-level exercises | Statement: [Fort Walker, hasTrainingCapability, brigade-level exercises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingCapability Context triple: [Fort Walker, hasTrainingCapability, brigade-level exercises]
-
A.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
B.
hasTrainingComplex
Indicates that an entity possesses or is associated with a dedicated facility or complex used for training activities.
-
C.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
-
D.
hasTrainingFunction
Indicates that one entity serves as a training function or mechanism for another entity.
-
E.
hasTrainingType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of training.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf9135bc8190a48a2e5cbafca0cd |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.