Triple
T7392645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opel Corsa |
E170538
|
entity |
| Predicate | primaryBodyConfiguration |
P8243
|
FINISHED |
| Object | hatchback |
—
|
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: hatchback | Statement: [Opel Corsa, primaryBodyConfiguration, hatchback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBodyConfiguration Context triple: [Opel Corsa, primaryBodyConfiguration, hatchback]
-
A.
primaryBody
Indicates that one entity serves as the main or principal body associated with another entity.
-
B.
primaryBodyStyle
chosen
Indicates the main or predominant body configuration or structural form associated with an entity.
-
C.
bodyConfiguration
Indicates the specific physical arrangement, posture, or structural setup of an entity’s body in relation to its parts or environment.
-
D.
primaryBodyType
Indicates the main physical form or category that characterizes an entity’s overall body structure or composition.
-
E.
primaryBodyAdvised
Indicates that one entity has been formally advised or counseled by another entity that serves as its main or primary advising body.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f224790c819099ceb7c7ac8d00f6 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.