Triple
T9002108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVD |
E215060
|
entity |
| Predicate | regionCoding |
P45385
|
FINISHED |
| Object | DVD region code |
—
|
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: DVD region code | Statement: [DVD, regionCoding, DVD region code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCoding Context triple: [DVD, regionCoding, DVD region code]
-
A.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
B.
regionCodeLevel
Indicates the hierarchical level or granularity associated with a given regional code within an administrative or geographic coding system.
-
C.
segmentCode
Indicates a code that identifies or classifies a specific segment within a larger structure, sequence, or process.
-
D.
regionCodeSystem
chosen
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
-
E.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6956a6e08190bd3853a7c1c130eb |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.