Triple
T19738033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1972–73 Kentucky Colonels |
E474038
|
entity |
| Predicate | regularSeasonRecordWins |
P14873
|
FINISHED |
| Object | 68 |
—
|
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: 68 | Statement: [1972–73 Kentucky Colonels, regularSeasonRecordWins, 68]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeasonRecordWins Context triple: [1972–73 Kentucky Colonels, regularSeasonRecordWins, 68]
-
A.
regularSeasonWins
chosen
Indicates the number of games a team wins during the regular season of a competition.
-
B.
regularSeasonWinsRecordNote
Indicates a note or special remark associated with an entity’s regular season wins record, such as exceptions, conditions, or clarifications about how that record was achieved or recorded.
-
C.
seasonRecordWins
Indicates the number of games a team has won during a specific season.
-
D.
bestRegularSeasonWins
Indicates the number of wins a team achieved in its most successful regular season.
-
E.
seasonWins
Indicates the number of games or competitions a team or individual has won during a specific 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6515f6efc8190a3da113847464399 |
completed | April 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.