Triple
T25177446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XMP |
E630485
|
entity |
| Predicate | supportsMetadataSchema |
P71375
|
FINISHED |
| Object | Dublin Core |
—
|
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 | Statement: [XMP, supportsMetadataSchema, Dublin Core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMetadataSchema Context triple: [XMP, supportsMetadataSchema, Dublin Core]
-
A.
supportsRecordSchemas
chosen
Indicates that one entity is capable of handling, validating, or operating with specified record schemas defined by another entity.
-
B.
hasMetadata
Indicates that one entity is associated with descriptive or informational data about another entity.
-
C.
dynamicMetadataSupport
Indicates that the subject system or component is capable of handling metadata that can change or be updated at runtime rather than being fixed or static.
-
D.
hasSchemaLanguage
Indicates that an entity uses, conforms to, or is defined in a particular schema language.
-
E.
isMetadataOnly
Indicates that the referenced item exists solely as descriptive or structural metadata and does not include the actual underlying content or data.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 12:34 p.m.