Triple
T11180985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000–01 NBA season |
E264535
|
entity |
| Predicate | introducedDefensiveThreeSeconds |
P97711
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2000–01 NBA season, introducedDefensiveThreeSeconds, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedDefensiveThreeSeconds Context triple: [2000–01 NBA season, introducedDefensiveThreeSeconds, true]
-
A.
shotClock
Indicates that a time limit is imposed on an offensive possession or action, after which a violation occurs if a shot or required attempt has not been made.
-
B.
shotClockDuration
Indicates the length of time allotted on the shot clock for a team to attempt a shot before a violation occurs.
-
C.
startOfDefense
Indicates the point in time or event at which a defense or defensive action begins.
-
D.
usedThreePointLine
Indicates that an action or play involved or was executed from beyond the three-point line.
-
E.
hasDefensivePositions
Indicates that an entity possesses or controls locations, structures, or arrangements specifically organized for defense against potential threats or attacks.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8a7f35481909f35feb94ef10e80 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.