Triple
T29447133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Active Suspension Management |
E746881
|
entity |
| Predicate | modeExample |
P88941
|
FINISHED |
| Object | Normal mode |
—
|
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: Normal mode | Statement: [Porsche Active Suspension Management, modeExample, Normal mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeExample Context triple: [Porsche Active Suspension Management, modeExample, Normal mode]
-
A.
modeExamples
chosen
Indicates that specific example instances are provided to illustrate or clarify a particular mode or manner in which something operates or occurs.
-
B.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
C.
mode
Indicates the manner, method, or way in which an action, process, or interaction is carried out or occurs.
-
D.
modeADescription
Indicates the descriptive text or explanation associated with a particular mode of operation or state.
-
E.
modeBDescription
Indicates the descriptive label or explanation associated with a specific operational or behavioral mode B.
- 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_69f66b21ea908190ae69b3f802fadab1 |
completed | May 2, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:28 p.m.