Triple
T11308808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 NCAA Division I men's basketball tournament |
E267784
|
entity |
| Predicate | notableGameRound |
P98423
|
FINISHED |
| Object | East Regional Final |
—
|
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: East Regional Final | Statement: [1992 NCAA Division I men's basketball tournament, notableGameRound, East Regional Final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameRound Context triple: [1992 NCAA Division I men's basketball tournament, notableGameRound, East Regional Final]
-
A.
notableGameEvent
Indicates that a specific game is associated with a significant or noteworthy event in its history or context.
-
B.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
C.
game5NotableEvent
Indicates that a notable or significant event occurred during the fifth game in a series or sequence.
-
D.
game1NotableEvent
Indicates that a specific event is recognized as a notable or significant occurrence within the context of game1.
-
E.
game6NotableEvent
Indicates that a notable event occurred during game 6 of a series or competition involving the related entities.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9bf87d88190904c2d174578ebbf |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.