Triple
T21814273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Conference men’s basketball tournament |
E538558
|
entity |
| Predicate | isBracketed |
P11195
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Southern Conference men’s basketball tournament, isBracketed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBracketed Context triple: [Southern Conference men’s basketball tournament, isBracketed, true]
-
A.
hasBracket
chosen
Indicates that one entity possesses, includes, or is associated with a bracket component or structure.
-
B.
usesBracket
Indicates that one entity employs or incorporates a bracket as a structural or functional component in relation to another entity.
-
C.
typeOfBracket
Indicates a relationship where one entity specifies the particular kind or category of bracket that another entity is associated with or uses.
-
D.
hasBracing
Indicates that one entity is structurally supported, reinforced, or stabilized by another entity acting as bracing.
-
E.
bracketIsBilinear
Indicates that the bracket operation is linear in each of its two arguments when the other is held fixed.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc8e6808190bde4d0e0981e4117 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.