Triple
T7198304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stryker armored fighting vehicle |
E168671
|
entity |
| Predicate | mobilityClass |
P11888
|
FINISHED |
| Object | highly mobile |
—
|
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: highly mobile | Statement: [Stryker armored fighting vehicle, mobilityClass, highly mobile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobilityClass Context triple: [Stryker armored fighting vehicle, mobilityClass, highly mobile]
-
A.
mobilityCharacteristic
chosen
Indicates a relationship where an entity is described or classified in terms of its movement or transportation-related properties, such as how, how well, or under what conditions it can move or be moved.
-
B.
mobilityRole
Indicates the functional role or capacity an entity has in enabling, supporting, or performing movement or transportation.
-
C.
mobilityComponent
Indicates that one entity functions as a mobility-related component or module that enables or affects the movement capabilities of another entity.
-
D.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
E.
vehicleFamily
Indicates that two vehicles belong to the same family or category based on shared design, platform, or lineage.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6e92a5d288190955f703470e75bf3 |
completed | March 27, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.