Triple
T9601016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Eaton |
E231849
|
entity |
| Predicate | singleSeasonBlocksPerGameRecord |
P89156
|
FINISHED |
| Object | 5.56 blocks per game in 1984–85 |
—
|
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: 5.56 blocks per game in 1984–85 | Statement: [Mark Eaton, singleSeasonBlocksPerGameRecord, 5.56 blocks per game in 1984–85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleSeasonBlocksPerGameRecord Context triple: [Mark Eaton, singleSeasonBlocksPerGameRecord, 5.56 blocks per game in 1984–85]
-
A.
bestSeasonRecord
Indicates that one entity holds the best (most successful) season performance record among a set of entities, typically in a competitive or statistical context.
-
B.
winsInSingleSeason
Indicates that one entity achieves a specified number of wins within a single competitive season.
-
C.
runnerUpRegularSeasonRecord
Indicates the regular season performance record (such as wins and losses) of the team that finished as runner-up.
-
D.
NBABlocksLeaderSeasons
Indicates the seasons in which a player led the NBA in blocked shots.
-
E.
hitsInSingleGameRecord
Indicates that an entity holds the record for the most hits achieved in a single game.
- F. None of above. chosen
Provenance (4 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a3934d481908400a63335d644bd |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:07 p.m.