Triple
T4481681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA South Region |
E100148
|
entity |
| Predicate | hasSeedingRange |
P56812
|
FINISHED |
| Object | 1 to 16 seeds |
—
|
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: 1 to 16 seeds | Statement: [NCAA South Region, hasSeedingRange, 1 to 16 seeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeedingRange Context triple: [NCAA South Region, hasSeedingRange, 1 to 16 seeds]
-
A.
hasSeeding
Indicates that an entity is assigned or associated with a specific seeding position or rank, typically for ordering or placement in a competitive or structured context.
-
B.
hasSeedCount
Indicates that an entity possesses a specific number of seeds.
-
C.
hasSeed
Indicates that one entity contains, produces, or is characterized by the presence of a seed associated with another entity.
-
D.
usesSeeding
Indicates that an entity employs a seeding process or strategy to initiate, distribute, or propagate something (such as data, content, or resources).
-
E.
determinesSeedingFor
Indicates that one entity is used to decide or assign the ranking, placement, or initial position (seeding) of another entity within a structured order or competition.
- F. None of above. chosen
Provenance (4 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
| PDg | Predicate description generation | batch_69b35727a8ac819090420bd3e2cfbcf1 |
completed | March 13, 2026, 12:15 a.m. |
Created at: March 12, 2026, 11:36 p.m.