Triple
T13556893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HDR10 |
E323797
|
entity |
| Predicate | dynamicMetadataSupport |
P110345
|
FINISHED |
| Object | not supported |
—
|
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: not supported | Statement: [HDR10, dynamicMetadataSupport, not supported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynamicMetadataSupport Context triple: [HDR10, dynamicMetadataSupport, not supported]
-
A.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with another entity.
-
B.
microdataAvailability
Indicates that detailed, record-level data (microdata) associated with an entity is available for access or use.
-
C.
dynamicFeatures
Indicates that an entity possesses or supports features whose presence, behavior, or configuration can change at runtime or in response to varying conditions.
-
D.
storesMetadataIn
Indicates that one entity holds or maintains descriptive or configuration metadata about another entity within a specified storage location or system.
-
E.
metadataLocation
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
- F. None of above. chosen
Provenance (4 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:47 p.m.