Triple
T32575819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Soccer League (post-2006) |
E832641
|
entity |
| Predicate | playsOutdoorSoccer |
P10057
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Canadian Soccer League (post-2006), playsOutdoorSoccer, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsOutdoorSoccer Context triple: [Canadian Soccer League (post-2006), playsOutdoorSoccer, yes]
-
A.
playsOutdoor
chosen
Indicates that an entity engages in an activity or game in an outdoor environment.
-
B.
playsAssociationFootballIn
Indicates that an entity participates in playing association football (soccer) within or for a specified place, organization, or context.
-
C.
playsFootballCode
Indicates that an entity participates in or is involved with a specific code or variant of football (e.g., soccer, rugby, American football).
-
D.
homeSoccerField
Indicates that a particular soccer field serves as the designated home field for a given team or organization.
-
E.
playedAssociationFootball
Indicates that an entity has participated in playing the sport of association football (soccer).
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:04 a.m.