Triple
T9068294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simple Knowledge Organization System |
E217298
|
entity |
| Predicate | coreProperty |
P28215
|
FINISHED |
| Object | skos:prefLabel |
—
|
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: skos:prefLabel | Statement: [Simple Knowledge Organization System, coreProperty, skos:prefLabel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreProperty Context triple: [Simple Knowledge Organization System, coreProperty, skos:prefLabel]
-
A.
metaProperty
chosen
Indicates that one property functions as a higher-level descriptor or attribute about another property, rather than about an entity directly.
-
B.
coreAttribute
Indicates that one attribute is a fundamental, defining, or essential property of another entity.
-
C.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
-
D.
closureProperty
Indicates that applying a specified operation to elements of a set always produces an element that is still within that same set.
-
E.
universalProperty
Indicates that a property or characteristic holds for all members of a specified set or domain without exception.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc94bf4f2881908c881e6ee7203994 |
completed | April 1, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:11 p.m.