Triple
T2392676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Division |
E48976
|
entity |
| Predicate | usesStandingsFor |
P10473
|
FINISHED |
| Object | playoff seeding |
—
|
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: playoff seeding | Statement: [Pacific Division, usesStandingsFor, playoff seeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStandingsFor Context triple: [Pacific Division, usesStandingsFor, playoff seeding]
-
A.
hasStandings
Indicates that an entity possesses or is associated with a set of rankings, positions, or status levels within a competitive or comparative context.
-
B.
usesRegularSeasonStandingsFor
chosen
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
C.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
D.
stateLeague
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
-
E.
supportsChampionshipsOf
Indicates that one entity provides backing, resources, or endorsement for the championships associated with another entity.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc87587708190a7f2bc473a898bc2 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.