Triple
T31816003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAM VCLC |
E812133
|
entity |
| Predicate | designedForTerrain |
P20426
|
FINISHED |
| Object | off-road operations |
—
|
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: off-road operations | Statement: [TAM VCLC, designedForTerrain, off-road operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForTerrain Context triple: [TAM VCLC, designedForTerrain, off-road operations]
-
A.
terrainCapability
chosen
Indicates the types of terrain or ground conditions in which an entity can effectively operate or function.
-
B.
involvesTerrain
Indicates that the relationship or action takes place in, across, or is directly affected by a specified type of terrain or landform.
-
C.
designedForLocation
Indicates that something has been created or configured specifically to be used in, or suited to, a particular location.
-
D.
hasGeneralTerrain
Indicates that an entity is characterized by or associated with a particular overall type of terrain.
-
E.
hasAdvancedTerrain
Indicates that an entity possesses or is associated with terrain featuring complex, challenging, or enhanced physical characteristics beyond standard ground conditions.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 30, 2026, 11:44 p.m.