Triple
T10998424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 USL W-League championship |
E259942
|
entity |
| Predicate | seasonEndingMatch |
P18737
|
FINISHED |
| Object | 2010 USL W-League season |
—
|
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: 2010 USL W-League season | Statement: [2010 USL W-League championship, seasonEndingMatch, 2010 USL W-League season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonEndingMatch Context triple: [2010 USL W-League championship, seasonEndingMatch, 2010 USL W-League season]
-
A.
postseasonEnd
Indicates the point in time or event at which a sports league’s postseason (playoffs) concludes.
-
B.
closedSeason
Indicates that a period of time is designated during which a particular activity (such as hunting, fishing, or harvesting) is legally prohibited or restricted.
-
C.
endSeason
Indicates the action or event of bringing a particular season, series, or period to a close.
-
D.
seasonCulminatesIn
chosen
Indicates that a particular season reaches its peak, conclusion, or defining outcome in the specified event or state.
-
E.
contractEndSeason
Indicates the season in which a contract or agreement is scheduled to end.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d3b08c81909376cd73c42fcefe |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e93ac648190b46c5d12bf3eb1e9 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.