Triple
T31047561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-AMG GLS 63 |
E791169
|
entity |
| Predicate | previousEngineFamily |
P126220
|
FINISHED |
| Object | M157 |
—
|
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: M157 | Statement: [Mercedes-AMG GLS 63, previousEngineFamily, M157]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousEngineFamily Context triple: [Mercedes-AMG GLS 63, previousEngineFamily, M157]
-
A.
successorEngineFamily
Indicates that one engine family directly follows and replaces another in a product or development lineage.
-
B.
belongsToEngineFamily
chosen
Indicates that an engine is a member of, or classified under, a specific engine family or series.
-
C.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
D.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
-
E.
notableEngineFamily
Indicates that one entity is a well-known or significant engine family associated with the other 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 29, 2026, 9 p.m.