Triple
T34631489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colgate Raiders men's lacrosse |
E889300
|
entity |
| Predicate | playsInMonthRange |
P181292
|
FINISHED |
| Object | February–May |
—
|
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: February–May | Statement: [Colgate Raiders men's lacrosse, playsInMonthRange, February–May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsInMonthRange Context triple: [Colgate Raiders men's lacrosse, playsInMonthRange, February–May]
-
A.
playedBetween
Indicates that an event, game, or match occurred involving two specified entities as participants or opposing sides.
-
B.
occasionallyPlayedInMonth
Indicates that an entity is played or used intermittently or on some, but not all, occasions within a given month.
-
C.
playedOnDate
Indicates that an event or activity (such as a game, performance, or match) occurred on a specific calendar date.
-
D.
recordedBetween
Indicates that an event or data item was recorded at a time that falls within a specified start and end time interval.
-
E.
playsInSeason
Indicates that an entity participates or performs in a specific season of an ongoing series, competition, or event.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: May 1, 2026, 2:04 a.m.