Triple
T5433092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 24748 |
E121542
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | ISO/IEC 24748-3 |
E121542
|
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/IEC 24748-3 | Statement: [ISO/IEC 24748, hasPart, ISO/IEC 24748-3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO/IEC 24748-3 Context triple: [ISO/IEC 24748, hasPart, ISO/IEC 24748-3]
-
A.
ISO/IEC 24748
chosen
ISO/IEC 24748 is an international standard that provides guidance on the application and management of systems and software life cycle processes defined in standards such as ISO/IEC 15288.
-
B.
ISO/IEC 23273
ISO/IEC 23273 is an international standard that specifies safety requirements for hydrogen-fueled road vehicles, particularly focusing on fuel cell vehicle safety.
-
C.
ISO/IEC 19757-3
ISO/IEC 19757-3 is an international standard that defines Schematron, a rule-based schema language for validating the structure and content of XML documents.
-
D.
ISO/IEC 25436
ISO/IEC 25436 is the international standard that formally defines the Eiffel programming language.
-
E.
ISO/IEC 30170
ISO/IEC 30170 is an international standard that formally specifies the Ruby 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd91ae18cc8190aefe610f91b5382c |
completed | March 20, 2026, 6:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf6c5c053c8190a53df1b6b5088aab |
completed | March 22, 2026, 4:13 a.m. |
Created at: March 20, 2026, 2:06 p.m.