Triple
T37164052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISDB |
E920747
|
entity |
| Predicate | supportsElectronicProgramGuide |
P205769
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ISDB, supportsElectronicProgramGuide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsElectronicProgramGuide Context triple: [ISDB, supportsElectronicProgramGuide, true]
-
A.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
B.
supportsMobileTVStandard
Indicates that one entity is compatible with or implements a specified mobile TV broadcasting standard for use on mobile devices.
-
C.
supportsStreamingServices
Indicates that one entity provides compatibility or functionality enabling the use of streaming services for another entity.
-
D.
hasDVB-H
Indicates that an entity is equipped with or supports DVB-H (Digital Video Broadcasting - Handheld) technology.
-
E.
operatesTelevisionService
Indicates that one entity runs or provides television broadcasting or TV-related services for another entity or area.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:15 p.m.