Triple
T780552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midwest Region |
E16485
|
entity |
| Predicate | hasBracketSize |
P11195
|
FINISHED |
| Object | 16-team regional bracket |
—
|
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: 16-team regional bracket | Statement: [Midwest Region, hasBracketSize, 16-team regional bracket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBracketSize Context triple: [Midwest Region, hasBracketSize, 16-team regional bracket]
-
A.
hasBracket
chosen
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
-
B.
hasBracketPosition
Indicates that an entity occupies or is assigned a specific position within a bracket or ordered bracket structure.
-
C.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
D.
hasRelativeSize
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
-
E.
hasLotSize
Indicates that an entity possesses a specific amount or extent of physical area, typically referring to the size of a parcel of land or property lot.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a90365648190ace53b0f0e87aa68 |
completed | March 1, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69a4a50bd23081908908235b8ec9201e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.