Triple
T10219646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Sloan Sports Analytics Conference |
E242539
|
entity |
| Predicate | typicalStartYear |
P92813
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [MIT Sloan Sports Analytics Conference, typicalStartYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartYear Context triple: [MIT Sloan Sports Analytics Conference, typicalStartYear, 2007]
-
A.
productionStartYear
Indicates the year in which the production of an item, work, or entity first began.
-
B.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
C.
laterTypeStartYear
Indicates that the starting year of one type or classification occurs later in time than the starting year of another type or classification.
-
D.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
E.
recordStartYear
Indicates the calendar year in which a particular record, entry, or data instance first began or was created.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa715a3c8190a9ccee7bcece0346 |
completed | April 6, 2026, 12:43 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_69d3aa208c248190a0fb186b106389f3 |
completed | April 6, 2026, 12:42 p.m. |
Created at: April 6, 2026, 11:08 a.m.