Triple
T30405693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 NCAA Division I men's basketball championship |
E773471
|
entity |
| Predicate | indianaScore |
P173749
|
FINISHED |
| Object | 52 |
—
|
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: 52 | Statement: [2002 NCAA Division I men's basketball championship, indianaScore, 52]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indianaScore Context triple: [2002 NCAA Division I men's basketball championship, indianaScore, 52]
-
A.
Indiana StateScore
Indicates that there is a score or scoring value associated with the state of Indiana.
-
B.
populationRankInIndiana
Indicates the relative position of an entity’s population size compared to other entities within the state of Indiana.
-
C.
Indiana StateCoach
Indicates that a person holds or has held the position of coach for an Indiana State University athletic team.
-
D.
Indiana StateRecordEnteringGame
Indicates that a team or player is entering a game holding a state-level record in Indiana.
-
E.
OregonScore
Indicates a scoring event or point total achieved by an entity in the context of Oregon (such as a game, test, or evaluation associated with Oregon).
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 29, 2026, 8:03 p.m.