Triple
T13426118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally1 |
E313485
|
entity |
| Predicate | replacesChassisConcept |
P34931
|
FINISHED |
| Object | production-based bodyshell |
—
|
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: production-based bodyshell | Statement: [Rally1, replacesChassisConcept, production-based bodyshell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesChassisConcept Context triple: [Rally1, replacesChassisConcept, production-based bodyshell]
-
A.
replacesConcept
chosen
Indicates that one concept takes the place of, or supersedes, another concept in a given context or system.
-
B.
usedChassisFor
Indicates that one entity employed or incorporated another entity’s chassis as the structural base or framework for its construction or operation.
-
C.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
-
D.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
-
E.
chassisCode
Indicates the specific chassis designation or code assigned to a vehicle model to distinguish its underlying structural platform or variant.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.