Triple
T33331055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 NCAA Division I men's basketball championship |
E853405
|
entity |
| Predicate | subeventOf |
P9823
|
FINISHED |
| Object | 1997 NCAA Final Four |
—
|
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: 1997 NCAA Final Four | Statement: [1997 NCAA Division I men's basketball championship, subeventOf, 1997 NCAA Final Four]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subeventOf Context triple: [1997 NCAA Division I men's basketball championship, subeventOf, 1997 NCAA Final Four]
-
A.
hasSubEvent
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
B.
partOfEvent
chosen
Indicates that one entity is a component, segment, or sub-activity that belongs to or occurs within a larger event.
-
C.
submissionTypeCoMainEvent
Indicates that the submission is classified as a co-main event within an event or program hierarchy.
-
D.
alsoHostedEventType
Indicates that the same host was responsible for organizing or holding another event of a specified type.
-
E.
tookPlaceAtEvent
Indicates that an action or occurrence happened during or in the context of a specific event.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.