Triple
T13687556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 NCAA Division I Men’s Basketball Regional |
E328169
|
entity |
| Predicate | totalTeamsInRegionals |
P111170
|
FINISHED |
| Object | 16 |
—
|
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 | Statement: [2004 NCAA Division I Men’s Basketball Regional, totalTeamsInRegionals, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalTeamsInRegionals Context triple: [2004 NCAA Division I Men’s Basketball Regional, totalTeamsInRegionals, 16]
-
A.
regionalsNumber
Indicates the number of regional-level instances (such as events, competitions, or units) associated with an entity.
-
B.
typicalNumberOfSuperRegionals
Indicates the usual or standard count of super-regional units or events associated with an entity.
-
C.
numberOfFinalTournamentTeams
Indicates the total count of teams that participate in the final stage of a tournament.
-
D.
numberOfParticipatingTeamsInQualifying
Indicates the total number of teams that take part in the qualifying stage of a competition or event.
-
E.
numberOfRegions
Indicates the total count of distinct regions associated with or contained within a given entity.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc670968881908e2b4fdf656c7285 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.