Triple
T29784424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural |
E756221
|
entity |
| Predicate | hasDriveConfigurations |
P138434
|
FINISHED |
| Object | 6x6 |
—
|
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: 6x6 | Statement: [Ural, hasDriveConfigurations, 6x6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDriveConfigurations Context triple: [Ural, hasDriveConfigurations, 6x6]
-
A.
hasCarConfiguration
chosen
Indicates that an entity is associated with a specific car configuration, detailing how the car is set up or specified.
-
B.
hasDriveNumberRange
Indicates that an entity is associated with a specific range of drive numbers, typically defining the minimum and maximum identifiers for drives it encompasses.
-
C.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
D.
hasTouringConfiguration
Indicates that an entity is associated with a specific setup or arrangement used for touring activities.
-
E.
hasDriver
Indicates that an entity is operated, controlled, or driven by a specific person or agent.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674a9cc8481909068fcdcc8ed7dab |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:07 p.m.