Triple
T25718032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCMES |
E644910
|
entity |
| Predicate | hasApplicationProfile |
P9523
|
FINISHED |
| Object | Dublin Core Application Profile |
—
|
NE NERFINISHED |
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: Dublin Core Application Profile | Statement: [DCMES, hasApplicationProfile, Dublin Core Application Profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApplicationProfile Context triple: [DCMES, hasApplicationProfile, Dublin Core Application Profile]
-
A.
hasApplicationType
Indicates that an entity is associated with or classified by a specific type or category of application.
-
B.
hasProfile
chosen
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
C.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
-
D.
hasAlternativeProfile
Indicates that an entity is associated with another profile that serves as an alternative or secondary representation of it.
-
E.
supportsDeviceProfiles
Indicates that one entity is capable of recognizing, handling, or operating with specified device configuration profiles.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 21, 2026, 9:48 p.m.