Triple
T38335857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMW M340i |
E1037953
|
entity |
| Predicate | differentialFeature |
P18160
|
FINISHED |
| Object | M Sport differential |
—
|
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: M Sport differential | Statement: [BMW M340i, differentialFeature, M Sport differential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differentialFeature Context triple: [BMW M340i, differentialFeature, M Sport differential]
-
A.
alternativeSplicingFeature
Indicates that a genomic region or element participates in an alternative splicing event, distinguishing it as a feature involved in generating splice variants.
-
B.
distinguishingTrait
Indicates that a particular characteristic or feature uniquely differentiates one entity from another.
-
C.
empiricalFeature
Indicates that a feature or property is derived from observation or experiment rather than theory or assumption.
-
D.
differential
Indicates a relationship where one quantity or state is defined as the infinitesimal change or difference relative to another variable or function.
-
E.
hasDistinctFeature
chosen
Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.