Triple
T12823961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 NCAA Tournament |
E306600
|
entity |
| Predicate | fieldExpansionStatus |
P40548
|
FINISHED |
| Object | 65-team format |
—
|
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: 65-team format | Statement: [2006 NCAA Tournament, fieldExpansionStatus, 65-team format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldExpansionStatus Context triple: [2006 NCAA Tournament, fieldExpansionStatus, 65-team format]
-
A.
expansionStatus
chosen
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
-
B.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
C.
fieldExtensionOf
Indicates that one field is an extension of another, meaning it contains the smaller field as a subfield and enlarges it by adding new elements while preserving field operations.
-
D.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
E.
supportedExpansionOf
Indicates that one entity actively aided, endorsed, or facilitated the growth, extension, or enlargement of another entity or domain.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96edcc99c8190986cd78fe4714835 |
completed | April 10, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:32 p.m.