Triple
T28660542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WMTW |
E725454
|
entity |
| Predicate | broadcastAreaIncludes |
P2441
|
FINISHED |
| Object | Portland, Maine |
—
|
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: Portland, Maine | Statement: [WMTW, broadcastAreaIncludes, Portland, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastAreaIncludes Context triple: [WMTW, broadcastAreaIncludes, Portland, Maine]
-
A.
broadcastRegion
chosen
Indicates the geographic area or market in which content is transmitted or made available for broadcast.
-
B.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
-
C.
broadcastSector
Indicates that an entity is associated with, operates in, or targets a particular broadcast sector or segment of the broadcasting domain.
-
D.
broadcastAsPartOf
Indicates that one broadcast event occurs as a component or segment within a larger, overarching broadcast.
-
E.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 4:57 a.m.