Triple
T30891419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STD 16 |
E786906
|
entity |
| Predicate | hasVersioningPolicy |
P7002
|
FINISHED |
| Object | Can be updated or obsoleted by later standards |
—
|
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: Can be updated or obsoleted by later standards | Statement: [STD 16, hasVersioningPolicy, Can be updated or obsoleted by later standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersioningPolicy Context triple: [STD 16, hasVersioningPolicy, Can be updated or obsoleted by later standards]
-
A.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
B.
hasVersionCount
Indicates the total number of distinct versions associated with a given entity.
-
C.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
D.
hasUpdatePolicy
chosen
Indicates that one entity defines or is associated with the rules or strategy governing how another entity is updated or maintained over time.
-
E.
hasVersionType
Indicates that one entity is associated with a specific kind or category of version of another entity.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:49 p.m.