Triple
T8700714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group C (2018 FIFA World Cup) |
E206522
|
entity |
| Predicate | containsMatchday |
P78680
|
FINISHED |
| Object | Matchday 1 |
—
|
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: Matchday 1 | Statement: [Group C (2018 FIFA World Cup), containsMatchday, Matchday 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMatchday Context triple: [Group C (2018 FIFA World Cup), containsMatchday, Matchday 1]
-
A.
matchdayElement
chosen
Indicates a relationship where an element (such as a game, event, or component) is part of or associated with a specific matchday.
-
B.
typicalMatchDay
Indicates that the relationship or conditions described correspond to what normally happens on a standard or usual match day.
-
C.
matchdayActivity
Indicates the specific activity, event, or engagement that takes place in connection with a particular match day.
-
D.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
E.
matchdayLocation
Indicates the venue or place where a particular matchday or game is held.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58b27bd48190a5f76111ee657553 |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.