Triple
T7942011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Lakers 2019–20 NBA season |
E184412
|
entity |
| Predicate | LeBronJamesPointsPerGame |
P52811
|
FINISHED |
| Object | 25.3 |
—
|
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: 25.3 | Statement: [Los Angeles Lakers 2019–20 NBA season, LeBronJamesPointsPerGame, 25.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LeBronJamesPointsPerGame Context triple: [Los Angeles Lakers 2019–20 NBA season, LeBronJamesPointsPerGame, 25.3]
-
A.
featuredLeBronJames
Indicates that an entity prominently highlighted, showcased, or focused on LeBron James in some context.
-
B.
pointsPerGame
chosen
Indicates the average number of points an entity scores per game over a given set of games.
-
C.
careerPointsPerGame
Indicates the average number of points an individual scores per game over the course of their entire career.
-
D.
teamLeBronCaptain
Indicates that the specified person holds the role of captain for Team LeBron.
-
E.
scoringAverageOver30PPGSeason
Indicates that an entity (typically a player) has recorded a season with a scoring average exceeding 30 points per game.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0c16b8819093c5d1719cd65ee3 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.