Triple
T2260357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VBCI |
E50023
|
entity |
| Predicate | vehicleConfiguration |
P25458
|
FINISHED |
| Object | 8×8 wheeled |
—
|
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: 8×8 wheeled | Statement: [VBCI, vehicleConfiguration, 8×8 wheeled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleConfiguration Context triple: [VBCI, vehicleConfiguration, 8×8 wheeled]
-
A.
featuresVehicle
Indicates that one entity includes, presents, or prominently incorporates a particular vehicle as part of its content, composition, or offering.
-
B.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
C.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
-
D.
transportCharacteristic
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
-
E.
equipmentCharacteristic
chosen
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.