Triple
T13426895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFL |
E313502
|
entity |
| Predicate | organizedSeasonFormat |
P2147
|
FINISHED |
| Object | round-robin league |
—
|
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: round-robin league | Statement: [SFL, organizedSeasonFormat, round-robin league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedSeasonFormat Context triple: [SFL, organizedSeasonFormat, round-robin league]
-
A.
permanentFormatFromSeason
Indicates that a permanent format or structure is derived from, or established based on, a particular season.
-
B.
seasonStructure
chosen
Indicates how a season is organized or structured in terms of its component parts, phases, or format.
-
C.
expandedFormatFromSeason
Indicates that one entity is an expanded or extended version of another entity that originates from a specific season.
-
D.
firstSeasonFormat
Indicates the specific format or structure in which the first season of something (such as a series or competition) was originally presented.
-
E.
organizesGamesPerSeason
Indicates that an entity is responsible for arranging or coordinating games according to each 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed1f9208190bf5ef5b8a7ded376 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.