Triple
T10168034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8824 |
E235255
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object | Abstract Syntax Notation One |
E42565
|
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: Abstract Syntax Notation One | Statement: [ISO/IEC 8824, defines, Abstract Syntax Notation One]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abstract Syntax Notation One Context triple: [ISO/IEC 8824, defines, Abstract Syntax Notation One]
-
A.
ASN.1
chosen
ASN.1 (Abstract Syntax Notation One) is a standardized, platform-independent notation used to define and encode complex data structures in telecommunications and cryptographic protocols, including X.509 certificates.
-
B.
Backus–Naur Form
Backus–Naur Form is a formal notation used to define the syntax of programming languages and other formal grammars in a precise, structured way.
-
C.
Augmented Backus–Naur Form
Augmented Backus–Naur Form (ABNF) is a standardized, extended version of Backus–Naur Form used to formally specify the syntax of languages and protocols, notably in Internet and communication standards.
-
D.
Van Wijngaarden grammars
Van Wijngaarden grammars are a highly expressive formal grammar formalism, introduced for defining complex programming language syntax and semantics, notably used in the specification of ALGOL 68.
-
E.
Yet Another Markup Language
Yet Another Markup Language is a human-readable data serialization format commonly used for configuration files and data exchange in programming and DevOps environments.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6f64a48190883aefce58a65ca6 |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d300ebacb88190850cf2242309b6ba |
completed | April 6, 2026, 12:40 a.m. |
Created at: March 30, 2026, 9:10 p.m.