Triple
T9171748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manitoba Moose |
E220095
|
entity |
| Predicate | seasonLengthType |
P2147
|
FINISHED |
| Object | AHL regular season plus playoffs |
—
|
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: AHL regular season plus playoffs | Statement: [Manitoba Moose, seasonLengthType, AHL regular season plus playoffs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonLengthType Context triple: [Manitoba Moose, seasonLengthType, AHL regular season plus playoffs]
-
A.
seasonDuration
Indicates the length of time that a particular season lasts.
-
B.
seasonStructure
chosen
Indicates how a season is organized or structured in terms of its component parts, phases, or format.
-
C.
playedSeasonType
Indicates that an entity participated in or was involved with a particular type of season (e.g., regular season, playoffs, preseason) within a competition or schedule.
-
D.
seasonNumber
Indicates the ordinal position of a season within a series or sequence of seasons.
-
E.
seasonSequence
Indicates the ordered succession relationship between seasons, specifying which season follows or precedes another in a temporal sequence.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae38ee48190bf783477bc37913d |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.