Triple
T16645834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Division of the 2021 NWSL Challenge Cup |
E404466
|
entity |
| Predicate | isWomenOnly |
P55024
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East Division of the 2021 NWSL Challenge Cup, isWomenOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWomenOnly Context triple: [East Division of the 2021 NWSL Challenge Cup, isWomenOnly, true]
-
A.
isSingleSex
Indicates that the entity involves or is restricted to only one biological sex or gender, rather than being mixed or coeducational.
-
B.
isGenderSpecificCategory
chosen
Indicates that the category applies specifically to one gender rather than being gender-neutral.
-
C.
hasGenderRequirement
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
D.
includesWomenStructure
Indicates that the referenced entity contains or incorporates a structural component specifically designed for or involving women.
-
E.
hasFemaleEquivalent
Indicates that one entity serves as the female counterpart or equivalent of another entity.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad59540819093765b7a67320f72 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e296af2f88819092c9ffee4a65d7dd |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.