Triple
T29447270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Communication Management |
E746884
|
entity |
| Predicate | positionInVehicle |
P138565
|
FINISHED |
| Object | center console |
—
|
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: center console | Statement: [Porsche Communication Management, positionInVehicle, center console]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInVehicle Context triple: [Porsche Communication Management, positionInVehicle, center console]
-
A.
driverPosition
Indicates the spatial or role-based position of a driver relative to a vehicle or driving context.
-
B.
positionInTrain
Indicates the relative location or ordering of an entity within the sequence of cars or sections that make up a train.
-
C.
occursInVehicle
Indicates that an event or action takes place within or on a vehicle.
-
D.
livesInVehicle
Indicates that an entity resides or habitually stays within a vehicle as its primary place of living or presence.
-
E.
positionOnSystem
chosen
Indicates the relative location or placement of an entity within a larger structured system or framework.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 28, 2026, 3:28 p.m.