Triple
T13578555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz SL 600 |
E324348
|
entity |
| Predicate | marketedAs |
P1395
|
FINISHED |
| Object | SL 600 |
E324348
|
NE 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: SL 600 | Statement: [Mercedes-Benz SL 600, marketedAs, SL 600]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SL 600 Context triple: [Mercedes-Benz SL 600, marketedAs, SL 600]
-
A.
Mercedes-Benz SL 600
chosen
The Mercedes-Benz SL 600 is a high-end luxury roadster distinguished by its powerful V12 engine, advanced technology, and refined grand-touring comfort.
-
B.
Mercedes-Benz SL 500
The Mercedes-Benz SL 500 is a luxury grand touring roadster renowned for its powerful V8 engine, refined comfort, and advanced technology within the SL-Class lineup.
-
C.
SLK
SLK is the FAA airport code for Adirondack Regional Airport, a public airport serving the Saranac Lake and Lake Placid region in New York.
-
D.
SLK
SLK is the vehicle registration code used on license plates for the town of Aschersleben in Germany.
-
E.
Mercedes-Benz SL 65 AMG
The Mercedes-Benz SL 65 AMG is a high-performance, V12-powered luxury roadster developed by Mercedes-AMG as the range-topping variant of the SL-Class.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02de1988190af2d473973ecd529 |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bbbe3c08190a359dfe7c3c8f15c |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.