Triple
T4298409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 NWSL Challenge Cup |
E99772
|
entity |
| Predicate | heldInPlaceOf |
P55319
|
FINISHED |
| Object | 2020 National Women's Soccer League regular 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: 2020 National Women's Soccer League regular season | Statement: [2020 NWSL Challenge Cup, heldInPlaceOf, 2020 National Women's Soccer League regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldInPlaceOf Context triple: [2020 NWSL Challenge Cup, heldInPlaceOf, 2020 National Women's Soccer League regular season]
-
A.
placeHeld
Indicates that an entity occupies or is located at a specific place or position.
-
B.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
C.
meetsInPlaceOf
Indicates that one entity meets or comes together with another specifically at a designated place or location.
-
D.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
E.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509d39348190aa83304661230cba |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:08 p.m.