Triple
T13252375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 National Women's Soccer League season |
E315563
|
entity |
| Predicate | finalMatches |
P109159
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [2015 National Women's Soccer League season, finalMatches, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMatches Context triple: [2015 National Women's Soccer League season, finalMatches, 1]
-
A.
finalsMatchup
Indicates that two competitors or teams are paired to face each other in the final round of a competition or tournament.
-
B.
divisionFinalsMatchup
Indicates a competitive pairing between two entities in the final round of a division-level contest or tournament.
-
C.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
-
D.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
E.
finalMatchDate
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
- F. None of above. chosen
Provenance (4 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:24 p.m.