Triple
T2542376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA Rookie of the Year Award |
E57812
|
entity |
| Predicate | statisticsConsidered |
P39440
|
FINISHED |
| Object | points |
—
|
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: points | Statement: [NBA Rookie of the Year Award, statisticsConsidered, points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statisticsConsidered Context triple: [NBA Rookie of the Year Award, statisticsConsidered, points]
-
A.
statisticsType
Indicates the specific kind or category of statistical measure or analysis associated with an entity or dataset.
-
B.
hasStatistics
Indicates that an entity is associated with one or more statistical measures, records, or summaries describing its quantitative properties or performance.
-
C.
statisticalDefinitionUsedBy
Indicates that a particular statistical definition is employed or applied by a given entity (such as a method, model, or analysis).
-
D.
hasStatisticalFunctions
Indicates that one entity provides or supports statistical operations or capabilities for another entity.
-
E.
obeysStatistics
Indicates that one entity’s behavior or outcomes conform to, follow, or are governed by statistical laws or patterns.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bd92f88190bf100c799f62210c |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:47 p.m.