Triple
T6033650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office Open XML (ECMA-376) |
E134365
|
entity |
| Predicate | approvedAsISOIECStandard |
P8040
|
FINISHED |
| Object | 2008 |
—
|
LITERAL 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: 2008 | Statement: [Office Open XML (ECMA-376), approvedAsISOIECStandard, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvedAsISOIECStandard Context triple: [Office Open XML (ECMA-376), approvedAsISOIECStandard, 2008]
-
A.
firstStandardApproved
Indicates that an entity is the earliest or initial standard that has received formal approval.
-
B.
OSIApproved
Indicates that a software license has been reviewed and approved by the Open Source Initiative (OSI) as complying with its Open Source Definition.
-
C.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
standardizationStatus
chosen
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
E.
isPartOfStandard
Indicates that something belongs to, is included within, or conforms to a defined standard or standardized set.
- F. None of above.
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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b220608190b156be95632cf3b3 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.