Triple
T25388042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stryker brigade combat team |
E631577
|
entity |
| Predicate | coreVehicleType |
P109335
|
FINISHED |
| Object | Stryker Infantry Carrier Vehicle |
—
|
NE NERFINISHED |
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: Stryker Infantry Carrier Vehicle | Statement: [Stryker brigade combat team, coreVehicleType, Stryker Infantry Carrier Vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreVehicleType Context triple: [Stryker brigade combat team, coreVehicleType, Stryker Infantry Carrier Vehicle]
-
A.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
B.
mainVehicleClass
chosen
Indicates the primary category or type of vehicle to which an entity chiefly belongs.
-
C.
poweredVehicleFamily
Indicates that one vehicle is part of a family or group of vehicles that share a common powered (motorized) design or platform.
-
D.
vehicleFamily
Indicates that two vehicles belong to the same family or category based on shared design, platform, or lineage.
-
E.
vehicleTypeFocus
Indicates that the relationship or action specifically concerns or emphasizes a particular type or category of vehicle.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5656c16ac8190be99d40cb63f9541 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:47 p.m.