Triple
T16318112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry McReynolds |
E396222
|
entity |
| Predicate | transitionedToBroadcasting |
P116542
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Larry McReynolds, transitionedToBroadcasting, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionedToBroadcasting Context triple: [Larry McReynolds, transitionedToBroadcasting, 2001]
-
A.
broadcastingUseBegan
chosen
Indicates that the use of a broadcasting service or capability has started at a specific point in time.
-
B.
broadcastBegan
Indicates that the transmission or airing of a broadcast has started.
-
C.
wasBroadcastOn
Indicates that a media item (such as a program, episode, or event) was transmitted or aired via a particular broadcast channel, station, or network.
-
D.
broadcastRuntime
Indicates that an entity transmits or distributes content or data during its execution period or operational timeframe.
-
E.
firstBroadcastAsPartOf
Indicates that an entity’s first broadcast occurred as a component or segment within a larger program, series, or event rather than as a standalone broadcast.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b3e3e081908a996b3e57ca4e32 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.