Triple
T37073517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outdoor Life Network |
E917645
|
entity |
| Predicate | hadProgramming |
P187313
|
FINISHED |
| Object | Tour de France coverage |
—
|
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: Tour de France coverage | Statement: [Outdoor Life Network, hadProgramming, Tour de France coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadProgramming Context triple: [Outdoor Life Network, hadProgramming, Tour de France coverage]
-
A.
hadProgrammingPeriod
Indicates that an entity experienced or was associated with a specific span of time during which programming activities took place.
-
B.
hasProgrammingFrom
Indicates that something derives its programming, configuration, or behavioral instructions from a specified source.
-
C.
hasProgrammingTheme
Indicates that something involves, is centered around, or is characterized by programming-related concepts, activities, or content.
-
D.
famousProgram
Indicates that a program is widely recognized or well-known, typically for its impact, quality, or popularity.
-
E.
hasProgrammingDomain
Indicates that an entity is associated with or specializes in a particular programming domain or area of software development.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb34e4906c8190abb1c293fb84329a |
completed | May 6, 2026, 12:32 p.m. |
Created at: May 3, 2026, 4:14 p.m.