Triple
T2978267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz 300 SL Gullwing |
E80449
|
entity |
| Predicate | engineCode |
P44382
|
FINISHED |
| Object | M198 |
—
|
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: M198 | Statement: [Mercedes-Benz 300 SL Gullwing, engineCode, M198]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineCode Context triple: [Mercedes-Benz 300 SL Gullwing, engineCode, M198]
-
A.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
B.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
C.
eraCode
Indicates the specific historical or temporal era associated with an entity, typically encoded as a standardized era identifier.
-
D.
hasEngineProgram
Indicates that an entity is associated with or participates in a specific engine-related program.
-
E.
drivingCode
Indicates that one entity is the driving or causal code responsible for initiating, controlling, or determining the behavior or outcome of another entity.
- F. None of above. chosen
Provenance (4 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999b0d50819093dac7678b887a9b |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.