Triple
T13801870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA 50–40–90 club |
E331660
|
entity |
| Predicate | statType |
P38911
|
FINISHED |
| Object | percentage-based statistic |
—
|
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: percentage-based statistic | Statement: [NBA 50–40–90 club, statType, percentage-based statistic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statType Context triple: [NBA 50–40–90 club, statType, percentage-based statistic]
-
A.
statisticsType
chosen
Indicates the specific kind or category of statistical measure or analysis associated with an entity or dataset.
-
B.
statisticalType
Indicates that one entity specifies the kind or category of statistical characterization or measurement that applies to another entity.
-
C.
statValue
Indicates that an entity has a particular statistical attribute with a specified value.
-
D.
statutoryType
Indicates the specific legal or statutory category under which something is formally classified or regulated.
-
E.
statisticNote
Indicates that there is an explanatory note or comment providing additional context or clarification about a reported statistic.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ded6c8190851c108ae559a355 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.