Triple
T19474610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 College World Series |
E487210
|
entity |
| Predicate | bracket |
P11195
|
FINISHED |
| Object | Bracket 1 |
—
|
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: Bracket 1 | Statement: [2008 College World Series, bracket, Bracket 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bracket Context triple: [2008 College World Series, bracket, Bracket 1]
-
A.
usesBracket
Indicates that one entity employs or incorporates a bracket as a structural or functional component in relation to another entity.
-
B.
hasBracket
chosen
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
-
C.
bracketSize
Indicates the size or capacity of a bracket used to group or structure related elements.
-
D.
typeOfBracket
Indicates a relationship where one entity specifies the particular kind or category of bracket that another entity is associated with or uses.
-
E.
bracketNotNecessarilyAssociative
Indicates that the bracketing operation on elements does not in general satisfy the associative law, so changing the grouping of operands can change the result.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633ef69508190b0d71ef663ba8977 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.