Triple
T34615525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish Superliga |
E888851
|
entity |
| Predicate | secondaryMatchDay |
P64902
|
FINISHED |
| Object | weekdays |
—
|
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: weekdays | Statement: [Danish Superliga, secondaryMatchDay, weekdays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryMatchDay Context triple: [Danish Superliga, secondaryMatchDay, weekdays]
-
A.
secondRoundDate
Indicates the date on which the second round of an event, process, or sequence is scheduled or occurs.
-
B.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
C.
secondBoutDate
Indicates the date on which a second bout, match, or occurrence of an event takes place.
-
D.
typicalMatchDay
chosen
Indicates that the relationship or conditions described correspond to what normally happens on a standard or usual match day.
-
E.
secondRoundEndDate
Indicates the date on which the second round of an event, process, or activity concludes.
- F. None of above.
Provenance (3 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: May 1, 2026, 2:03 a.m.