Triple
T29982500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weissach axle independent suspension |
E761632
|
entity |
| Predicate | locationNamedAfter |
P87205
|
FINISHED |
| Object | Porsche Weissach Development Center |
—
|
NE NERFINISHED |
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: Porsche Weissach Development Center | Statement: [Weissach axle independent suspension, locationNamedAfter, Porsche Weissach Development Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationNamedAfter Context triple: [Weissach axle independent suspension, locationNamedAfter, Porsche Weissach Development Center]
-
A.
placeNamedAfterBy
chosen
Indicates that one entity serves as the namesake for a place, meaning the place is named after that entity.
-
B.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
C.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
-
D.
fieldOfNamedAfter
Indicates that a field of study or professional discipline is named in honor of a particular person or entity.
-
E.
placeNamedAfterEvent
Indicates that a place derives its name from a specific historical event or occurrence.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: April 29, 2026, 6:35 p.m.