Triple
T29447232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Ceramic Composite Brakes |
E746883
|
entity |
| Predicate | weightAdvantageComparedTo |
P167966
|
FINISHED |
| Object | cast iron brake discs |
—
|
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: cast iron brake discs | Statement: [Porsche Ceramic Composite Brakes, weightAdvantageComparedTo, cast iron brake discs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightAdvantageComparedTo Context triple: [Porsche Ceramic Composite Brakes, weightAdvantageComparedTo, cast iron brake discs]
-
A.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
B.
isHeavierThan
Indicates that one entity has greater weight or mass than another entity.
-
C.
weightCondition
Indicates that a specified weight-related requirement or constraint holds between entities or values.
-
D.
weightReductionComparedTo
chosen
Indicates a comparison showing how much less weight one entity has relative to another.
-
E.
weightStandardInfluencedBy
Indicates that a weight standard is affected, shaped, or determined by another factor, standard, or influence.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 3:28 p.m.