Triple
T24637762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millennium Flood |
E609858
|
entity |
| Predicate | mediaCoverageInLanguage |
P156870
|
FINISHED |
| Object | Polish |
—
|
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: Polish | Statement: [Millennium Flood, mediaCoverageInLanguage, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaCoverageInLanguage Context triple: [Millennium Flood, mediaCoverageInLanguage, Polish]
-
A.
mediaCoverageAs
Indicates that one entity provides or receives media coverage in the role, capacity, or format specified by another entity.
-
B.
mediaCoverage
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
C.
mediaCoverageFocus
Indicates the primary topic, subject, or aspect that media coverage is centered on or emphasizes.
-
D.
mediaCoverageContext
Indicates the situational background, circumstances, or framing within which media coverage of an entity, event, or issue takes place.
-
E.
mediaLanguage
Indicates the language in which a media item (such as a film, broadcast, or publication) is originally produced or presented.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:33 a.m.