Triple
T34844130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minneapolis Regional |
E1004420
|
entity |
| Predicate | tournamentRoundScope |
P178553
|
FINISHED |
| Object | regional rounds |
—
|
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: regional rounds | Statement: [Minneapolis Regional, tournamentRoundScope, regional rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentRoundScope Context triple: [Minneapolis Regional, tournamentRoundScope, regional rounds]
-
A.
roundsPerTournament
Indicates the number of rounds that occur within a single tournament.
-
B.
tournamentSection
chosen
Indicates that an entity is a specific section, division, or bracket within a larger tournament.
-
C.
tournamentBracket
Indicates the structured competitive relationship among participants in a tournament, showing who faces whom and how winners advance through successive rounds.
-
D.
tournamentMatches
Indicates that a tournament includes or schedules specific matches as part of its competitive structure.
-
E.
tournamentUse
Indicates that a tournament utilizes or is conducted using a particular resource, format, rule set, or venue.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.