Triple
T7149483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NY6 |
E166655
|
entity |
| Predicate | semifinalRotation |
P9731
|
FINISHED |
| Object | two bowls host semifinals each season |
—
|
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: two bowls host semifinals each season | Statement: [NY6, semifinalRotation, two bowls host semifinals each season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semifinalRotation Context triple: [NY6, semifinalRotation, two bowls host semifinals each season]
-
A.
usesRotationForSemifinals
chosen
Indicates that a rotation system is employed to determine participation or ordering in the semifinals stage of a competition or process.
-
B.
semifinalMatchup
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
-
C.
semifinalResult
Indicates the outcome or score of a semifinal-stage contest or match between competitors.
-
D.
secondSeedByeToSemifinals
Indicates that the competitor seeded second advances directly to the semifinals without having to play in earlier rounds (a bye).
-
E.
semiFinalsHeld
Indicates that the semi-final stage of a competition or tournament has taken place or is being conducted.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f130e08190bc5ca99f90f9de92 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.