Triple

T11060140
Position Surface form Disambiguated ID Type / Status
Subject QGIS E261485 entity
Predicate supportsVectorFormat P97573 FINISHED
Object DXF E758491 NE 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: DXF | Statement: [QGIS, supportsVectorFormat, DXF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DXF
Context triple: [QGIS, supportsVectorFormat, DXF]
  • A. DXF chosen
    DXF is a widely used CAD file format developed by Autodesk for exchanging drawing data between different design and drafting applications.
  • B. DWF
    DWF (Design Web Format) is a highly compressed, secure file format developed by Autodesk for efficiently sharing and viewing rich 2D and 3D design data.
  • C. NX Drafting
    NX Drafting is the Siemens NX module dedicated to creating, editing, and managing 2D engineering drawings from 3D CAD models.
  • D. FDF
    FDF is the IATA airport code for Martinique Aimé Césaire International Airport, the main air gateway to the Caribbean island of Martinique.
  • E. IGES
    IGES is a widely used neutral file format standard for exchanging 2D and 3D CAD data between different computer-aided design systems.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aa98650481908609c7c56bfa7902 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d798e991848190b07c2f48dae38681 completed April 9, 2026, 12:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3c87ab0308190a6a6ada1708f0ec2 completed April 18, 2026, 6:07 p.m.
Created at: April 8, 2026, 9:26 p.m.