Triple
T7325953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA blocks leader |
E168875
|
entity |
| Predicate | statisticMeasured |
P75344
|
FINISHED |
| Object | blocked shots per game |
—
|
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: blocked shots per game | Statement: [NBA blocks leader, statisticMeasured, blocked shots per game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statisticMeasured Context triple: [NBA blocks leader, statisticMeasured, blocked shots per game]
-
A.
measured
Indicates that one entity has determined or quantified a property, amount, or extent of another entity using some standard or instrument.
-
B.
measuredProperty
Indicates that the subject is a measurement that quantifies or assesses the specified property of an entity.
-
C.
measuredBy
Indicates that something’s quantity, extent, or value is determined or expressed using a particular measurement method, instrument, or unit.
-
D.
measuredAs
Indicates that one entity’s quantity, value, or property is expressed or recorded using another entity as its measurement or unit.
-
E.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a612c08190b7a3fefa811bbcec |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e80ae5688190ac3d6c1bdf9532f0 |
completed | March 27, 2026, 8:26 p.m. |
Created at: March 27, 2026, 3:03 p.m.