Triple
T5295118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Mikan |
E119832
|
entity |
| Predicate | ruleChangesAttributed |
P19084
|
FINISHED |
| Object | widening of the lane in basketball |
—
|
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: widening of the lane in basketball | Statement: [George Mikan, ruleChangesAttributed, widening of the lane in basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleChangesAttributed Context triple: [George Mikan, ruleChangesAttributed, widening of the lane in basketball]
-
A.
typicalRuleModification
Indicates a change made to a standard or default rule, adjusting how that rule normally applies or operates.
-
B.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
C.
decorChanges
Indicates that an entity alters or updates the decorative appearance or arrangement of another entity or environment.
-
D.
claimsToModify
Indicates that one entity asserts it can change, alter, or adjust another entity or its properties.
-
E.
notableRuleChange
chosen
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.