Triple
T22197252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC JTC 1/SC 34 |
E548579
|
entity |
| Predicate | standardizes |
P1371
|
FINISHED |
| Object | ISO/IEC 29500 |
—
|
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: ISO/IEC 29500 | Statement: [ISO/IEC JTC 1/SC 34, standardizes, ISO/IEC 29500]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO/IEC 29500 Context triple: [ISO/IEC JTC 1/SC 34, standardizes, ISO/IEC 29500]
-
A.
ISO 32000
ISO 32000 is the international standard that defines the specifications and requirements for the Portable Document Format (PDF).
-
B.
ISO/IEC 26300
ISO/IEC 26300 is the international standard that defines the OpenDocument Format (ODF) for office documents such as text, spreadsheets, and presentations.
-
C.
Office Open XML (ECMA-376)
chosen
Office Open XML (ECMA-376) is a standardized, XML-based file format used primarily by Microsoft Office applications for representing word processing documents, spreadsheets, and presentations.
-
D.
ISO 19005
ISO 19005 is the ISO standard that defines the PDF/A format for long-term archiving of electronic documents.
-
E.
ISO/IEC 20922
ISO/IEC 20922 is the international standard that defines the MQTT lightweight publish/subscribe messaging protocol commonly used in IoT and machine-to-machine communication.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae7c72081909b7817d66391bef4 |
completed | April 28, 2026, 9:47 p.m. |
Created at: April 16, 2026, 8:35 p.m.