Triple
T11101393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisville Bats |
E262512
|
entity |
| Predicate | hasSeasonLength |
P97288
|
FINISHED |
| Object | Triple-A schedule length (typically 140+ games) |
—
|
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: Triple-A schedule length (typically 140+ games) | Statement: [Louisville Bats, hasSeasonLength, Triple-A schedule length (typically 140+ games)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonLength Context triple: [Louisville Bats, hasSeasonLength, Triple-A schedule length (typically 140+ games)]
-
A.
typicalSeasonSeriesLength
Indicates the usual number of episodes or installments that make up a single season of a series.
-
B.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
C.
hasSeasonFrequency
Indicates how often something occurs or is scheduled within a specific season.
-
D.
hasSeasonScope
Indicates that something is applicable, valid, or relevant only within a specified season or seasonal period.
-
E.
hasSeasonType
Indicates that something is associated with a particular category or type of season (e.g., summer, winter, rainy).
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2ab09081908ffce2df8912b657 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.