Triple
T8930220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAN TGS |
E212633
|
entity |
| Predicate | brakeAssist |
P4166
|
FINISHED |
| Object | ABS |
—
|
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: ABS | Statement: [MAN TGS, brakeAssist, ABS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brakeAssist Context triple: [MAN TGS, brakeAssist, ABS]
-
A.
brakeType
chosen
Indicates the specific kind or system of brakes associated with an entity.
-
B.
brakeSupplier
Indicates that one entity serves as the supplier or provider of brakes to another entity.
-
C.
brakeConfigurationSupport
Indicates that one entity provides or defines support for the brake configuration of another entity.
-
D.
brakeWear
Indicates that an entity is experiencing or exhibiting wear, degradation, or reduction in effectiveness of its braking components or braking function.
-
E.
associatedBreak
Indicates a relationship where one entity is linked to a specific break, interruption, or pause that is relevant to its state, schedule, or operation.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6676d5d881908ce78cbb5561a68b |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.