Triple
T24993910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysler DN platform (first generation) |
E625516
|
entity |
| Predicate | brakeTypeSupport |
P4166
|
FINISHED |
| Object | front disc brakes |
—
|
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: front disc brakes | Statement: [Chrysler DN platform (first generation), brakeTypeSupport, front disc brakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brakeTypeSupport Context triple: [Chrysler DN platform (first generation), brakeTypeSupport, front disc brakes]
-
A.
brakeConfigurationSupport
Indicates that one entity provides or defines support for the brake configuration of another entity.
-
B.
brakeType
chosen
Indicates the specific kind or system of brakes associated with an entity.
-
C.
brakeFeature
Indicates that an entity possesses or is equipped with a particular braking-related feature or capability.
-
D.
brakeSupplier
Indicates that one entity serves as the supplier or provider of brakes to another entity.
-
E.
brakeApplication
Indicates that a braking action is being applied to slow down or stop an entity.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:04 a.m.