Triple
T33671208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECHL Bakersfield Condors |
E862621
|
entity |
| Predicate | operatedUntilSeason |
P6603
|
FINISHED |
| Object | 2014–15 ECHL 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: 2014–15 ECHL season | Statement: [ECHL Bakersfield Condors, operatedUntilSeason, 2014–15 ECHL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUntilSeason Context triple: [ECHL Bakersfield Condors, operatedUntilSeason, 2014–15 ECHL season]
-
A.
operatedSeason
Indicates the specific season or time period during which an entity (such as a service, facility, or operation) was active or in use.
-
B.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
C.
endSeason
Indicates the action or event of bringing a particular season, series, or period to a close.
-
D.
season1EndDate
Indicates the calendar date on which the first season of something (e.g., a show, competition, or series) concludes.
-
E.
lastCompletedSeason
Indicates the most recent season of an ongoing or episodic series that has been fully finished or concluded.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:42 a.m.