Triple
T11194587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweden vs Mexico |
E264887
|
entity |
| Predicate | openingMatchStatus |
P23679
|
FINISHED |
| Object | tournament opener |
—
|
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: tournament opener | Statement: [Sweden vs Mexico, openingMatchStatus, tournament opener]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingMatchStatus Context triple: [Sweden vs Mexico, openingMatchStatus, tournament opener]
-
A.
openingMatchResult
Indicates the outcome or result associated with the opening match in a series, tournament, or competition.
-
B.
openingMatch
chosen
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
C.
openingMatchScore
Indicates the degree of similarity or compatibility between an opening (e.g., a position, role, or opportunity) and a given candidate or item, typically expressed as a numeric score.
-
D.
openingPractice
Indicates the practice or rehearsal of opening moves, procedures, or initial actions in a given context.
-
E.
openingRole
Indicates the functional role or position an entity holds at the initial or starting phase of an event, process, or sequence.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8bf14e481908563b15790af4d20 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.