Triple
T3575136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA men’s lacrosse |
E75667
|
entity |
| Predicate | shotClock |
P50673
|
FINISHED |
| Object | implemented at the NCAA level |
—
|
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: implemented at the NCAA level | Statement: [NCAA men’s lacrosse, shotClock, implemented at the NCAA level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shotClock Context triple: [NCAA men’s lacrosse, shotClock, implemented at the NCAA level]
-
A.
shotClockDuration
Indicates the length of time allotted on the shot clock for a team to attempt a shot before a violation occurs.
-
B.
shotType
Indicates the specific kind or category of shot used or taken in a given context (e.g., in film, photography, or sports).
-
C.
pointsNeededInFinalQuarter
Indicates the number of points a team or player must score in the final quarter to achieve a specific target or outcome.
-
D.
usesPitchClock
Indicates that an entity employs or is governed by a pitch clock to regulate the timing of pitches.
-
E.
decidedInRegulationTime
Indicates that the outcome of a contest or match was determined within the standard allotted duration, without requiring any extra time or tiebreak procedures.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0da77008190922f414b85b9cad4 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb8364d848190a96a9bc7a6126af2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:21 p.m.