Triple
T2571840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Division |
E57680
|
entity |
| Predicate | hasTiebreakerRule |
P6631
|
FINISHED |
| Object | crossover rule |
—
|
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: crossover rule | Statement: [East Division, hasTiebreakerRule, crossover rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTiebreakerRule Context triple: [East Division, hasTiebreakerRule, crossover rule]
-
A.
tiebreaker
chosen
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
B.
hasTieGame
Indicates that a game or match has ended with both sides having the same score, resulting in no winner.
-
C.
hasRulebook
Indicates that one entity possesses, is governed by, or is associated with a specific rulebook.
-
D.
hasDesignatedPlayerRule
Indicates that a sports league or competition uses a designated player rule allowing certain players to be treated differently for roster or salary purposes.
-
E.
hasSpecialRules
Indicates that certain entities are governed by additional or exceptional rules that differ from the standard ones.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd383dce881909411a38c6d37bc3a |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.