Triple
T27167238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moody Theater |
E682810
|
entity |
| Predicate | broadcastFormatSupported |
P31690
|
FINISHED |
| Object | high-definition television |
—
|
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: high-definition television | Statement: [Moody Theater, broadcastFormatSupported, high-definition television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastFormatSupported Context triple: [Moody Theater, broadcastFormatSupported, high-definition television]
-
A.
broadcastsInFormat
chosen
Indicates that a broadcasting entity transmits its content using a specified technical format or standard.
-
B.
audioFormatSupported
Indicates that a particular audio format is recognized and can be correctly processed or played by a given system or component.
-
C.
hasPlayFormat
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 9:21 a.m.