Triple
T17424714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern League |
E423708
|
entity |
| Predicate | followsSeasonFormat |
P117126
|
FINISHED |
| Object | annual home-and-away league 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: annual home-and-away league season | Statement: [Southern League, followsSeasonFormat, annual home-and-away league season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSeasonFormat Context triple: [Southern League, followsSeasonFormat, annual home-and-away league season]
-
A.
seasonFormatIncludes
chosen
Indicates that a particular season uses or contains a specified format as part of its structure or presentation.
-
B.
followedBySeason
Indicates that one season occurs immediately after another in chronological order.
-
C.
followsSeries
Indicates that one entity comes after another as the next installment or continuation within an ordered series.
-
D.
followsEpisode
Indicates that one episode occurs directly after another in a sequence or series.
-
E.
permanentFormatFromSeason
Indicates that a permanent format or structure is derived from, or established based on, a particular 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4423999ac81909fdbd8bcffcb30c9 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.