Triple
T1934699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blu-ray Disc |
E41417
|
entity |
| Predicate | supportsRegionCoding |
P21828
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Blu-ray Disc, supportsRegionCoding, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRegionCoding Context triple: [Blu-ray Disc, supportsRegionCoding, yes]
-
A.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
B.
supportsRegion
Indicates that one entity provides assistance, resources, or backing to a specific geographic or administrative region.
-
C.
supportsRegionRestriction
chosen
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
D.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb29b51408190afb2f918814e68c7 |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.