Triple

T11060168
Position Surface form Disambiguated ID Type / Status
Subject MapInfo Professional E261486 entity
Predicate fileFormatSupport P8463 FINISHED
Object CSV E35620 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: CSV | Statement: [MapInfo Professional, fileFormatSupport, CSV]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CSV
Context triple: [MapInfo Professional, fileFormatSupport, CSV]
  • A. CSV chosen
    CSV (Comma-Separated Values) is a simple, text-based file format commonly used to store and exchange tabular data between different software applications and systems.
  • B. CSV
    Conseil scolaire Viamonde (CSV) is a French-language public secular school board serving students in various regions of Ontario, Canada.
  • C. RFC 4180
    RFC 4180 is the Internet standard that formally specifies the common format and rules for Comma-Separated Values (CSV) files.
  • D. SXC
    SXC is the stock ticker symbol for SunCoke Energy, Inc., a U.S.-based producer of coke used in steelmaking and a provider of related logistics services.
  • E. RCFile
    RCFile is a columnar storage file format designed for efficient data processing and querying in Hadoop-based 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_69e3e75b90ec8190b1a799e0183c6784 completed April 18, 2026, 8:19 p.m.
Created at: April 8, 2026, 9:26 p.m.