Triple

T22709924
Position Surface form Disambiguated ID Type / Status
Subject Common Lisp Object System E561565 entity
Predicate standardizedIn P7508 FINISHED
Object ANSI X3.226-1994 NE NERFINISHED

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 X3.226-1994 | Statement: [Common Lisp Object System, standardizedIn, ANSI X3.226-1994]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ANSI X3.226-1994
Context triple: [Common Lisp Object System, standardizedIn, ANSI X3.226-1994]
  • A. ANSI X3.226-1994 chosen
    ANSI X3.226-1994 is the American National Standards Institute specification that formally defines the Common Lisp programming language.
  • B. ANSI X3.74-1987
    ANSI X3.74-1987 is an American National Standards Institute specification that formally defines the PL/I programming language.
  • C. ANSI X3.92
    ANSI X3.92 is a U.S. national standard that formally specifies the Data Encryption Standard (DES) symmetric-key cryptographic algorithm for commercial and government use.
  • D. ANSI X3.159-1989
    ANSI X3.159-1989 is the original American national standard that formally defined the C programming language.
  • E. ANSI INCITS 226-1994 (R2004)
    ANSI INCITS 226-1994 (R2004) is the American national standard that formally specifies the Common Lisp programming language.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2454f1348819088d83f420925a5c1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f178d1e24881909ebd4531c0daef7f completed April 29, 2026, 3:19 a.m.
Created at: April 17, 2026, 3:17 p.m.