Triple
T1131510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1946–47 BAA season |
E23040
|
entity |
| Predicate | topScorerPointsPerGame |
P18045
|
FINISHED |
| Object | 23.2 |
—
|
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: 23.2 | Statement: [1946–47 BAA season, topScorerPointsPerGame, 23.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topScorerPointsPerGame Context triple: [1946–47 BAA season, topScorerPointsPerGame, 23.2]
-
A.
topScorerPoints
chosen
Indicates the number of points scored by the top-scoring entity in a given context or event.
-
B.
topScorer
Indicates that the subject is the individual with the highest score among a specified group or in a particular context.
-
C.
careerPointsPerGame
Indicates the average number of points an individual scores per game over the course of their entire career.
-
D.
MVPGoals
Indicates that an entity has been recognized as the Most Valuable Player (MVP) based on achieving specific performance goals or criteria.
-
E.
MVPPoints
Indicates the number of points an entity has earned toward a Most Valuable Player (MVP) recognition or award.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.