Triple
T34099098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 International Champions Cup |
E874514
|
entity |
| Predicate | includesMatchesIn |
P205318
|
FINISHED |
| Object | North America |
E335
|
NE 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: North America | Statement: [2016 International Champions Cup, includesMatchesIn, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMatchesIn Context triple: [2016 International Champions Cup, includesMatchesIn, North America]
-
A.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
B.
includesMatchesFrom
Indicates that one entity contains or aggregates matches or matching results that originate from another source or context.
-
C.
includesMatchType
Indicates that one entity’s set or collection contains an element with a specified type of match (e.g., exact, partial, or pattern-based) to another entity.
-
D.
usesMatchesFrom
Indicates that one entity relies on or incorporates matches (e.g., pattern matches, rule matches, or result matches) produced by another entity or process.
-
E.
includesHits
Indicates that one entity contains or encompasses one or more hits, results, or matching items associated with another entity.
- F. None of above. chosen
Provenance (5 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36ae3ad7a0819084ee3c2461f4b619 |
completed | June 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:53 a.m.