Triple
T37164036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISDB |
E920747
|
entity |
| Predicate | usesMultiplexing |
P51279
|
FINISHED |
| Object | MPEG-2 Transport Stream |
—
|
NE NERFINISHED |
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: MPEG-2 Transport Stream | Statement: [ISDB, usesMultiplexing, MPEG-2 Transport Stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMultiplexing Context triple: [ISDB, usesMultiplexing, MPEG-2 Transport Stream]
-
A.
hasMultiplex
Indicates that one entity possesses or is associated with multiple instances or channels of another entity within a shared structure or system.
-
B.
multiplexing
chosen
Indicates combining multiple signals or data streams into a single channel or medium for transmission or processing.
-
C.
supportsMultipleStreams
Indicates that the subject is capable of handling or maintaining more than one data or communication stream at the same time.
-
D.
usesDuplexMethod
Indicates that one entity employs a duplex method, meaning a two-way or bidirectional technique or process, in relation to another entity or context.
-
E.
multiplexType
Indicates the specific kind or category of multiplex relationship or connection that exists between entities.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:15 p.m.