Triple
T10436191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian Basketball League |
E246044
|
entity |
| Predicate | includesRegularSeason |
P25200
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Romanian Basketball League, includesRegularSeason, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRegularSeason Context triple: [Romanian Basketball League, includesRegularSeason, yes]
-
A.
hasRegularSeason
chosen
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
B.
includesPostseasonIn
Indicates that a time period, schedule, or dataset explicitly encompasses postseason games or events in addition to the regular season.
-
C.
hasRegularSeasonCoverage
Indicates that an entity provides media or broadcast coverage of another entity’s regular season events or games.
-
D.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
E.
hasRegularSeasonImportance
Indicates that something possesses significance or relevance specifically within the context of a regular 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea843f1c8190afca4a42bc364468 |
completed | April 7, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:14 p.m.