Triple

T6009834
Position Surface form Disambiguated ID Type / Status
Subject Common Lisp E133804 entity
Predicate standardizationBody P1251 FINISHED
Object ANSI E6170 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: ANSI | Statement: [Common Lisp, standardizationBody, ANSI]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ANSI
Context triple: [Common Lisp, standardizationBody, ANSI]
  • A. ANSI chosen
    ANSI is a private non-profit organization that oversees the development and coordination of voluntary consensus standards for products, services, processes, and systems in the United States.
  • B. ISO 646
    ISO 646 is an international standard for 7-bit character encodings that defines a set of basic Latin characters and allows national variants, serving as a foundation for many early computer character sets.
  • C. ANSI X3.74-1987
    ANSI X3.74-1987 is an American National Standards Institute specification that formally defines the PL/I programming language.
  • D. ANSI X3.159-1989
    ANSI X3.159-1989 is the original American national standard that formally defined the C programming language.
  • E. ISO/IEC 2022
    ISO/IEC 2022 is an international standard that defines mechanisms for encoding and switching between multiple character sets within a single byte-oriented data stream.
  • 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_69c0087361a48190905c6b55969852b8 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04f4e27a881909cc3f7fef62abc3b completed March 22, 2026, 8:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1089bd870819096c0f6c7cf484c50 completed March 23, 2026, 9:32 a.m.
Created at: March 22, 2026, 4:06 p.m.