Triple
T37480185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHDTV1 |
E931391
|
entity |
| Predicate | hasScanningFormat |
P162703
|
FINISHED |
| Object | progressive |
—
|
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: progressive | Statement: [UHDTV1, hasScanningFormat, progressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScanningFormat Context triple: [UHDTV1, hasScanningFormat, progressive]
-
A.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
B.
scanFormat
chosen
Indicates the format or pattern used when scanning or parsing input data.
-
C.
hasCurrentFormat
Indicates that an entity currently exists, is stored, or is represented in a particular format.
-
D.
usesScanningMethod
Indicates that an entity performs or carries out an action by employing a specific scanning method.
-
E.
hasScanningCenter
Indicates that an entity is associated with, or makes use of, a particular scanning center for scanning-related activities.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: May 3, 2026, 4:17 p.m.