Triple
T183470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basketball Association of America |
E3927
|
entity |
| Predicate | regularSeasonFormat |
P2673
|
FINISHED |
| Object | round-robin schedule among member teams |
—
|
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 schedule among member teams | Statement: [Basketball Association of America, regularSeasonFormat, round-robin schedule among member teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonFormat Context triple: [Basketball Association of America, regularSeasonFormat, round-robin schedule among member teams]
-
A.
seasonStructure
Indicates how a season is organized or structured in terms of its component parts, phases, or format.
-
B.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
C.
overtimeFormatRegularSeason
Indicates the format or rules used for overtime periods specifically during the regular season.
-
D.
postseasonType
Indicates the specific kind of postseason competition or phase associated with an event or team.
-
E.
competitionSeason
Indicates that an entity is associated with a particular competitive season or edition of a competition.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25926be9c8190a4cfce66f57589d1 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566dfc388190988b1b42d5daaafe |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.