Triple
T688452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 NWSL Fall Series Community Shield |
E13336
|
entity |
| Predicate | podStructure |
P18255
|
FINISHED |
| Object | regional pods |
—
|
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: regional pods | Statement: [2020 NWSL Fall Series Community Shield, podStructure, regional pods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: podStructure Context triple: [2020 NWSL Fall Series Community Shield, podStructure, regional pods]
-
A.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
-
B.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
C.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
D.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
E.
secondLevelStructure
Indicates a relationship where one structure functions as a secondary or subordinate level within a larger, primary structure.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2048d48190ab99ab59accb6909 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a4a0f405748190ba72a9cfe946a8ec |
completed | March 1, 2026, 8:26 p.m. |
Created at: March 1, 2026, 7:36 p.m.