Triple
T24037793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 NCAA Division I men's basketball championship game |
E595282
|
entity |
| Predicate | featuresNicknamedTeam |
P5076
|
FINISHED |
| Object | Phi Slama Jama |
—
|
NE NERFINISHED |
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: Phi Slama Jama | Statement: [1984 NCAA Division I men's basketball championship game, featuresNicknamedTeam, Phi Slama Jama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNicknamedTeam Context triple: [1984 NCAA Division I men's basketball championship game, featuresNicknamedTeam, Phi Slama Jama]
-
A.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
B.
teamNickname
chosen
Indicates the commonly used informal or symbolic name by which a team is known.
-
C.
teamNameRefersTo
Indicates that a given team name designates or refers to a specific team entity.
-
D.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
-
E.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d6ce7c8190a41b2d9b459881bf |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:57 p.m.