Triple
T27217373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Express Newspapers |
E681174
|
entity |
| Predicate | hasWeekendEdition |
P165071
|
FINISHED |
| Object | Sunday Express |
—
|
NE NERFINISHED |
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: Sunday Express | Statement: [Express Newspapers, hasWeekendEdition, Sunday Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeekendEdition Context triple: [Express Newspapers, hasWeekendEdition, Sunday Express]
-
A.
hasWeekSystem
Indicates that one entity uses, follows, or is organized according to a particular system for dividing time into weeks.
-
B.
isAnnualEditionOf
Indicates that one entity is a specific yearly edition or version of another, typically recurring publication or event.
-
C.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
D.
isHolidaySpecialOf
Indicates that something is a special version, event, or offering specifically created for or associated with a particular holiday.
-
E.
newspaperSupplementOf
Indicates that one publication functions as a supplementary section or insert to a main newspaper.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 9:41 a.m.