Triple
T32443156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger Pro League |
E829067
|
entity |
| Predicate | broadcastOnline |
P17106
|
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: [Challenger Pro League, broadcastOnline, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastOnline Context triple: [Challenger Pro League, broadcastOnline, true]
-
A.
broadcastStatus
Indicates the current state or phase of a broadcast (e.g., scheduled, live, paused, or completed) in relation to the entities involved.
-
B.
broadcastDuring
Indicates that one event or program is broadcast while another specified time period or event is occurring.
-
C.
broadcastVia
chosen
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
-
D.
broadcastLiveFrom
Indicates that an event or program is being transmitted in real time from a specific location or source.
-
E.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 12:55 a.m.