Triple
T108745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox |
E2195
|
entity |
| Predicate | distributionPlatform |
P1486
|
FINISHED |
| Object | over-the-air broadcast |
—
|
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: over-the-air broadcast | Statement: [Fox, distributionPlatform, over-the-air broadcast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributionPlatform Context triple: [Fox, distributionPlatform, over-the-air broadcast]
-
A.
platforms
Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
-
B.
distributionMethod
chosen
Indicates the means or channel through which something (such as a product, resource, or information) is delivered or made available to recipients.
-
C.
distributor
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
-
D.
distribution
Indicates the act or pattern of giving, delivering, or spreading something from one source to multiple recipients or locations.
-
E.
operatingSystem
Indicates that one entity is the operating system running on, or used by, another entity.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563fd2fc819090265edbfe3092d6 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.