Triple
T12514160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | musl |
E299154
|
entity |
| Predicate | supportsStandard |
P1587
|
FINISHED |
| Object | ISO C99 |
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 C99 | Statement: [musl, supportsStandard, ISO C99]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO C99 Context triple: [musl, supportsStandard, ISO C99]
-
A.
ISO/IEC 9899
chosen
ISO/IEC 9899 is the international standard that defines the C programming language’s syntax, semantics, and library.
-
B.
C11
C11 is a London bus route that operates in northwest London, connecting areas such as Archway, Hampstead, and Brent Cross.
-
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 C18
ANSI C18 is a set of American National Standards that define the dimensions, performance, and safety requirements for portable primary and secondary batteries, including common consumer sizes like AAA cells.
-
E.
IEEE 796
IEEE 796 is the IEEE standard that formally defines the Multibus computer bus architecture used for modular, board-level system design.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9541e752c8190bf12d2b5a37b53df |
completed | April 10, 2026, 7:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64bbba5fc819082a4171a5a77183a |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:57 p.m.