Triple
T5733809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2019 |
E126449
|
entity |
| Predicate | hostDetermination |
P65041
|
FINISHED |
| Object | higher-seeded finalist hosted the match |
—
|
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: higher-seeded finalist hosted the match | Statement: [MLS Cup 2019, hostDetermination, higher-seeded finalist hosted the match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostDetermination Context triple: [MLS Cup 2019, hostDetermination, higher-seeded finalist hosted the match]
-
A.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
B.
hostSelection
Indicates the choice or designation of a particular host from a set of possible hosts for a given purpose or interaction.
-
C.
host
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
-
D.
typicalHostSelection
chosen
Indicates the usual or preferred choice of host entity that is selected in a given context or process.
-
E.
hostSystem
Indicates that one entity serves as the primary computing or operating environment in which another entity runs, is managed, or is contained.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.