Triple
T20634978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haldex all-wheel-drive system |
E507052
|
entity |
| Predicate | normallyOperatesAs |
P140852
|
FINISHED |
| Object | front-wheel-drive system |
—
|
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: front-wheel-drive system | Statement: [Haldex all-wheel-drive system, normallyOperatesAs, front-wheel-drive system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normallyOperatesAs Context triple: [Haldex all-wheel-drive system, normallyOperatesAs, front-wheel-drive system]
-
A.
normallyClosesAs
Indicates that one entity typically or by default closes or terminates in the state, condition, or configuration represented by another entity.
-
B.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
C.
formerOperates
Indicates that an entity previously operated or managed another entity but no longer does so.
-
D.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0e5fc481909e4f0dd7fb1203fc |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:42 a.m.