Triple
T10826308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C90 |
E255504
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | ANSI X3.159-1989 C standard |
E255505
|
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 X3.159-1989 C standard | Statement: [C90, basedOn, ANSI X3.159-1989 C standard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ANSI X3.159-1989 C standard Context triple: [C90, basedOn, ANSI X3.159-1989 C standard]
-
A.
ANSI X3.159-1989
chosen
ANSI X3.159-1989 is the original American national standard that formally defined the C programming language.
-
B.
ISO/IEC 9899
ISO/IEC 9899 is the international standard that defines the C programming language’s syntax, semantics, and library.
-
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.74-1987
ANSI X3.74-1987 is an American National Standards Institute specification that formally defines the PL/I programming language.
-
E.
ANSI X3.226-1994
ANSI X3.226-1994 is the American National Standards Institute specification that formally defines the Common Lisp programming language.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d1c24881909f56d56207cccbef |
completed | April 9, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de858672d8819094baf4fe98b8dea4 |
completed | April 14, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.