Triple
T31672995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Basketball Invitational |
E808321
|
entity |
| Predicate | usualFieldSize |
P7759
|
FINISHED |
| Object | 16 teams |
—
|
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 teams | Statement: [College Basketball Invitational, usualFieldSize, 16 teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usualFieldSize Context triple: [College Basketball Invitational, usualFieldSize, 16 teams]
-
A.
fieldSize
chosen
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
B.
sizeRestriction
Indicates that there is a limitation or constraint on the allowable size or dimensions of something in the relationship.
-
C.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
D.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
E.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:01 p.m.