Triple
T18754222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBA Regular Season |
E458605
|
entity |
| Predicate | usesStandingsSystem |
P94650
|
FINISHED |
| Object | win–loss record |
—
|
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: win–loss record | Statement: [CBA Regular Season, usesStandingsSystem, win–loss record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStandingsSystem Context triple: [CBA Regular Season, usesStandingsSystem, win–loss record]
-
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.
usesInStandingsTables
chosen
Indicates that something is employed or applied within standings tables, such as rankings or league tables, to represent or organize comparative positions.
-
C.
usesRegularSeasonStandingsFor
Indicates that one entity determines outcomes or decisions based on the regular season standings of another entity.
-
D.
usesQualificationSystem
Indicates that an entity applies or relies on a specific qualification system as part of its processes or operations.
-
E.
usesCompetitionSystem
Indicates that an entity operates under or applies a particular competition system or format.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ef4ee48190a9892ac9787ffe37 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.