Triple
T14013777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WLW |
E337152
|
entity |
| Predicate | carriedProgramming |
P112448
|
FINISHED |
| Object | Cincinnati Reds baseball games |
—
|
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: Cincinnati Reds baseball games | Statement: [WLW, carriedProgramming, Cincinnati Reds baseball games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedProgramming Context triple: [WLW, carriedProgramming, Cincinnati Reds baseball games]
-
A.
programType
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
B.
intendedProgram
Indicates the academic or training program that an entity plans or expects to pursue, rather than one they are currently enrolled in or have completed.
-
C.
relatesToProgram
Indicates that one entity has a relevant connection, association, or involvement with a particular program.
-
D.
carriedTo
Indicates that one entity transported or conveyed another entity from one place to another.
-
E.
famousProgram
Indicates that a program is widely recognized or well-known, typically for its impact, quality, or popularity.
- F. None of above. chosen
Provenance (4 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:19 p.m.