Triple
T727760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curiosity rover |
E14763
|
entity |
| Predicate | wheelConfiguration |
P5627
|
FINISHED |
| Object | rocker-bogie suspension |
—
|
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: rocker-bogie suspension | Statement: [Curiosity rover, wheelConfiguration, rocker-bogie suspension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelConfiguration Context triple: [Curiosity rover, wheelConfiguration, rocker-bogie suspension]
-
A.
wheelArrangementSystem
chosen
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
-
B.
wheelType
Indicates the specific kind or category of wheel associated with an entity.
-
C.
wheelbase
Indicates the distance between the centers of the front and rear wheels of a vehicle.
-
D.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
E.
featuresVehicle
Indicates that one entity includes, presents, or prominently incorporates a particular vehicle as part of its content, composition, or offering.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f839608190878a60eb7a044ed9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.