Triple
T18469775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996–97 American Basketball League season |
E451265
|
entity |
| Predicate | scheduleType |
P63521
|
FINISHED |
| Object | winter schedule |
—
|
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: winter schedule | Statement: [1996–97 American Basketball League season, scheduleType, winter schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduleType Context triple: [1996–97 American Basketball League season, scheduleType, winter schedule]
-
A.
schedulePattern
Indicates a recurring or structured timing relationship that defines when an event or action is scheduled to occur.
-
B.
recurrenceType
Indicates the pattern or frequency with which an event or action repeats over time.
-
C.
scheduledServiceType
Indicates the type or category of service that has been scheduled between entities (e.g., maintenance, appointment, or delivery).
-
D.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
E.
hasScheduleType
chosen
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5305e349c8190925166bc3dddb320 |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.