Triple
T10826262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C90 |
E255504
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | ISO C90 |
E51009
|
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: ISO C90 | Statement: [C90, alsoKnownAs, ISO C90]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO C90 Context triple: [C90, alsoKnownAs, ISO C90]
-
A.
ISO/IEC 9899
chosen
ISO/IEC 9899 is the international standard that defines the C programming language’s syntax, semantics, and library.
-
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.
ISO/IEC 14882
ISO/IEC 14882 is the international standard that formally defines the C++ programming language, including its core language features and standard library.
-
D.
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.
-
E.
IEEE 1496-1993
IEEE 1496-1993 is an IEEE standard that specifies the SBus computer bus architecture used primarily in Sun Microsystems workstations and servers.
- 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.