Triple
T30143766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Stability Control |
E766195
|
entity |
| Predicate | appliesBrakes |
P135935
|
FINISHED |
| Object | individual wheels selectively |
—
|
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: individual wheels selectively | Statement: [Electronic Stability Control, appliesBrakes, individual wheels selectively]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesBrakes Context triple: [Electronic Stability Control, appliesBrakes, individual wheels selectively]
-
A.
brakeApplication
chosen
Indicates that a braking action is being applied to slow down or stop an entity.
-
B.
hasBraking
Indicates that an entity possesses or is equipped with a braking capability or braking system.
-
C.
hasBrakingRole
Indicates that an entity participates in a braking process by fulfilling a specific braking-related function or responsibility.
-
D.
brakeFeature
Indicates that an entity possesses or is equipped with a particular braking-related feature or capability.
-
E.
brakeType
Indicates the specific kind or system of brakes associated with 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 29, 2026, 7:18 p.m.