Triple
T22218616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2023 NWSL Shield |
E549143
|
entity |
| Predicate | confersAdvantageIn |
P7339
|
FINISHED |
| Object | NWSL Playoffs seeding |
—
|
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: NWSL Playoffs seeding | Statement: [2023 NWSL Shield, confersAdvantageIn, NWSL Playoffs seeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confersAdvantageIn Context triple: [2023 NWSL Shield, confersAdvantageIn, NWSL Playoffs seeding]
-
A.
notableAdvantage
chosen
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
-
B.
advantageDefinition
Indicates that one entity defines or specifies the nature, scope, or meaning of an advantage associated with another entity.
-
C.
alternativeBenefit
Indicates that one benefit serves as a substitute or replacement for another possible benefit in a given context.
-
D.
contractingAdvantage
Indicates that one party has a favorable position, benefit, or leverage over another in the process of forming or negotiating a contract.
-
E.
regulatoryAdvantage
Indicates that one entity gains a favorable position or benefit over others due to laws, rules, or regulatory conditions.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8edd288190a49f10e009122057 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.