Triple
T16100861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permian Panthers |
E390614
|
entity |
| Predicate | timePeriodOfNotableSeason |
P7547
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Permian Panthers, timePeriodOfNotableSeason, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfNotableSeason Context triple: [Permian Panthers, timePeriodOfNotableSeason, 1988]
-
A.
notableSeason
chosen
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
B.
hasSeasonLength
Indicates that one entity has a specified duration or length for its season.
-
C.
typicalSeasonTiming
Indicates the usual time period or season during which something normally occurs or is expected to take place.
-
D.
seasonOfNotableEvent
Indicates the season of the year during which a notable event occurs or is recognized.
-
E.
notableSeasonAsOC
Indicates that an individual had a particularly significant or noteworthy season while serving as an offensive coordinator.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6756948190a7f5ecb375e59701 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.