Triple
T470235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL Premier Development League |
E8538
|
entity |
| Predicate | typicalSeasonStructure |
P2147
|
FINISHED |
| Object | regular season followed by playoffs |
—
|
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: regular season followed by playoffs | Statement: [USL Premier Development League, typicalSeasonStructure, regular season followed by playoffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSeasonStructure Context triple: [USL Premier Development League, typicalSeasonStructure, regular season followed by playoffs]
-
A.
seasonStructure
chosen
Indicates how a season is organized or structured in terms of its component parts, phases, or format.
-
B.
typicalStartSeason
Indicates the season during which something (such as an activity, event, or phenomenon) usually begins.
-
C.
seasonTypicalStartMonth
Indicates the calendar month in which a particular season usually begins.
-
D.
typicalSeasonMeetings
Indicates that there are regularly occurring meetings associated with a particular season or time period.
-
E.
typicalNumberOfMeetingsPerSeason
Indicates the usual or average count of meetings that occur within a single season.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efef8b788190857ebf66df562d59 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.