Triple
T22744814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario's Miracle |
E562518
|
entity |
| Predicate | distanceFromBasket |
P111425
|
FINISHED |
| Object | behind the three-point line |
—
|
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: behind the three-point line | Statement: [Mario's Miracle, distanceFromBasket, behind the three-point line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBasket Context triple: [Mario's Miracle, distanceFromBasket, behind the three-point line]
-
A.
basketHeight
Indicates the vertical distance from the ground or reference surface to the top or rim of a basket.
-
B.
capacityForBasketball
Indicates the ability or suitability of an entity to play or perform well in basketball.
-
C.
orientationToBasket
chosen
Indicates the directional alignment or facing of an entity relative to the position of the basket.
-
D.
haveTypicalApproachDistance
Indicates that there is a characteristic or standard distance typically maintained when approaching something.
-
E.
distanceFromBol
Indicates the measured distance between an entity and a specified beginning-of-line (BOL) reference point.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1797590f08190a784f73fcd27b101 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:23 p.m.