Triple

T2962764
Position Surface form Disambiguated ID Type / Status
Subject VR Commodore E80085 entity
Predicate frontDesign P45253 FINISHED
Object revised grille and headlamps compared with VP 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: revised grille and headlamps compared with VP | Statement: [VR Commodore, frontDesign, revised grille and headlamps compared with VP]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: frontDesign
Context triple: [VR Commodore, frontDesign, revised grille and headlamps compared with VP]
  • A. frontType
    Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
  • B. front
    Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
  • C. frontDesignSameAsBack
    Indicates that the design on the front side of an object is identical to the design on its back side.
  • D. frontSightType
    Indicates the specific kind or design of the front sight used on an object, typically a firearm or similar aiming device.
  • E. designBureau
    Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
  • 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_69ad8b1341848190bd19dbf46892887d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9955e6488190bea170724d5fbfe8 completed March 8, 2026, 3:44 p.m.
PD Predicate disambiguation batch_69ad960e71f8819088179d11248c6ed0 completed March 8, 2026, 3:30 p.m.
PDg Predicate description generation batch_69ad98379fac8190a4dfe530787703c9 completed March 8, 2026, 3:39 p.m.
Created at: March 8, 2026, 2:57 p.m.