Triple
T11056006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clásico Regio |
E261377
|
entity |
| Predicate | hasMediaCoverageLevel |
P97545
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [Clásico Regio, hasMediaCoverageLevel, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediaCoverageLevel Context triple: [Clásico Regio, hasMediaCoverageLevel, national]
-
A.
hasMediaCoverageSince
Indicates that an entity has had media coverage starting from a specified point in time and continuing from then onward.
-
B.
mediaCoverageAs
Indicates that one entity provides or receives media coverage in the role, capacity, or format specified by another entity.
-
C.
mediaCoverage
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
D.
hasPublisherCoverage
Indicates that a publisher provides content, services, or distribution that extend over or apply to a specified entity or area.
-
E.
mediaCoverageControversy
Indicates that media coverage is associated with, contributes to, or centers around a controversy involving the related entities.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a152b4819095b74a8996346077 |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.