Triple
T12370253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Sol |
E294980
|
entity |
| Predicate | playoffResult2009 |
P79927
|
FINISHED |
| Object | lost WPS Championship Game |
—
|
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: lost WPS Championship Game | Statement: [Los Angeles Sol, playoffResult2009, lost WPS Championship Game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffResult2009 Context triple: [Los Angeles Sol, playoffResult2009, lost WPS Championship Game]
-
A.
playoffResult
chosen
Indicates the outcome of a playoff contest or series between competitors, such as who advanced or was eliminated.
-
B.
playoffStatus2019
Indicates the relationship between an entity (such as a team or player) and its qualification or performance status in the 2019 playoffs.
-
C.
playoffRound
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
D.
playoffPoints
Indicates the number of points an entity has earned or been credited with in playoff or postseason competition.
-
E.
playoffPath
Indicates the sequence of games, rounds, or matchups a team or player must progress through in a playoff tournament.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d942a2d6e08190a13c7ff89af09354 |
completed | April 10, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69d93ecf6b548190a394b6b56a0c1c68 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.