Triple
T16641622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEC men's basketball honors |
E404350
|
entity |
| Predicate | seasonRecognized |
P14881
|
FINISHED |
| Object | regular season |
—
|
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: regular season | Statement: [SEC men's basketball honors, seasonRecognized, regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonRecognized Context triple: [SEC men's basketball honors, seasonRecognized, regular season]
-
A.
seasonLabel
Indicates the specific season (e.g., spring, summer, fall, winter, or a numbered TV season) associated with an entity.
-
B.
seasonCharacterization
chosen
Indicates how a particular season is described, defined, or characterized in terms of its qualities or attributes.
-
C.
sportSeasonOf
Indicates that one entity is a sports season that belongs to, or is part of, the overall history or schedule of the specified sport.
-
D.
season
Indicates that an entity participates in, is associated with, or occurs during a particular season or seasonal period.
-
E.
seasonCulminatesIn
Indicates that a particular season reaches its peak, conclusion, or defining outcome in the specified event or state.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad1a7748190aa9308d4e96c566c |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e296af2f88819092c9ffee4a65d7dd |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.