Triple
T7895934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC |
E183342
|
entity |
| Predicate | developsStandard |
P73
|
FINISHED |
| Object | ISO/IEC 25010 |
E183351
|
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 25010 | Statement: [ISO/IEC, developsStandard, ISO/IEC 25010]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO/IEC 25010 Context triple: [ISO/IEC, developsStandard, ISO/IEC 25010]
-
A.
ISO/IEC 25010
chosen
ISO/IEC 25010 is an international standard that defines a comprehensive quality model for software and systems, specifying characteristics and sub-characteristics used to evaluate product quality and quality in use.
-
B.
ISO/IEC 9126
ISO/IEC 9126 is an international standard that defines a quality model and related metrics for evaluating and describing software product quality.
-
C.
ISO/IEC 12207
ISO/IEC 12207 is an international standard that defines a comprehensive framework and set of processes for the life cycle management of software systems.
-
D.
IEEE 12207
IEEE 12207 is an international standard that defines processes, activities, and tasks for the life cycle management of software systems.
-
E.
ISO/IEC/IEEE 29148
ISO/IEC/IEEE 29148 is an international standard that defines best practices and processes for engineering and managing system and software requirements.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a174574819084270dbb6fcbb7fe |
completed | March 31, 2026, 3:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5bae4bdc8190be7db2ba3acb708a |
completed | March 31, 2026, 5:29 a.m. |
Created at: March 30, 2026, 5:01 p.m.