Triple
T7228319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maneuver Center of Excellence |
E154838
|
entity |
| Predicate | integratesCapability |
P75725
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [Maneuver Center of Excellence, integratesCapability, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesCapability Context triple: [Maneuver Center of Excellence, integratesCapability, infantry]
-
A.
associatedCapability
Indicates that one entity has a related ability, function, or competence that is linked to or relevant for another entity.
-
B.
providesCapabilityTo
Indicates that one entity enables or equips another entity with a specific capability or functionality.
-
C.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
D.
developedCapability
Indicates that an entity has created, acquired, or brought into existence a particular capability through its actions or processes.
-
E.
isPartOfCapability
Indicates that one capability is a component or sub-function within a broader, composite capability.
- F. None of above. chosen
Provenance (4 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9e0ba248190a57a3b4fa8b858c7 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:54 p.m.