Triple
T9601706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | softball |
E231864
|
entity |
| Predicate | standardPitchingDistanceSlowpitch |
P89168
|
FINISHED |
| Object | 50 feet or more depending on league |
—
|
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: 50 feet or more depending on league | Statement: [softball, standardPitchingDistanceSlowpitch, 50 feet or more depending on league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardPitchingDistanceSlowpitch Context triple: [softball, standardPitchingDistanceSlowpitch, 50 feet or more depending on league]
-
A.
distanceToHomePlate
Indicates the measured distance between an entity’s current position and home plate.
-
B.
fastballVelocity
Indicates the speed at which a fastball pitch travels, typically measured at or near home plate.
-
C.
noHitterLocation
Indicates the location or venue where a no-hitter game occurred.
-
D.
numberOfPitches
Indicates the total count of pitches involved in a given event, performance, or musical segment.
-
E.
capacityBaseball
Indicates the maximum number of spectators that a baseball venue is designed or allowed to hold.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a3a49608190ad1f65195e4d5cda |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:07 p.m.