Triple
T2909034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 NWSL Championship |
E63636
|
entity |
| Predicate | regularTimeScore |
P42688
|
FINISHED |
| Object | 1–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–1 | Statement: [2016 NWSL Championship, regularTimeScore, 1–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularTimeScore Context triple: [2016 NWSL Championship, regularTimeScore, 1–1]
-
A.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
B.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
C.
overtimeRule
Indicates the rule or policy that defines when and how overtime work is calculated or applied.
-
D.
overtimeFormatRegularSeason
Indicates the format or rules used for overtime periods specifically during the regular season.
-
E.
decidingScoreTime
Indicates the point in time at which a decisive or game-determining score occurs.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0d329c88190b6fcaef0be1799eb |
completed | March 7, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69abdd19bac881908f047d616aca8438 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:11 p.m.