Triple
T11074584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-CHOP |
E261830
|
entity |
| Predicate | alternativeSchedule |
P57562
|
FINISHED |
| Object | 14-day cycle (R-CHOP-14) |
—
|
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: 14-day cycle (R-CHOP-14) | Statement: [R-CHOP, alternativeSchedule, 14-day cycle (R-CHOP-14)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeSchedule Context triple: [R-CHOP, alternativeSchedule, 14-day cycle (R-CHOP-14)]
-
A.
alternativeEvent
Indicates that one event serves as an alternative or substitute option to another event within the same context.
-
B.
alternativePlan
chosen
Indicates that one plan serves as a substitute or backup option for another plan within the same context or objective.
-
C.
seasonSchedule
Indicates the planned timing and sequence of events, activities, or occurrences within a specific season.
-
D.
alternativeScoring
Indicates that there exists an additional or non-standard method of scoring or evaluation associated with the primary scoring system or context.
-
E.
rescheduledLosingTeam
Indicates that the team which originally lost had its game or match moved to a different time or date.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994efb608190a81bc8c4d16ddbd0 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.