Triple
T1194200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allan Houston |
E25629
|
entity |
| Predicate | pointsPerGameCareerAverage |
P10820
|
FINISHED |
| Object | 17.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: 17.3 | Statement: [Allan Houston, pointsPerGameCareerAverage, 17.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsPerGameCareerAverage Context triple: [Allan Houston, pointsPerGameCareerAverage, 17.3]
-
A.
careerPointsPerGame
chosen
Indicates the average number of points an individual scores per game over the course of their entire career.
-
B.
careerBlocksPerGame
Indicates the average number of blocked shots a player records per game over the course of their entire career.
-
C.
careerReboundsPerGame
Indicates the average number of rebounds a player records per game over the course of their entire career.
-
D.
careerRunsScored
Indicates the total number of runs an entity has scored over the entire duration of their playing career.
-
E.
scoredOverPointsCareer
Indicates that an entity (typically an athlete) accumulated more than a specified number of points over the course of their entire career.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd7743548190a70d3f3c7378aaa7 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.