Triple
T27546417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 NBA All-Star Game |
E695373
|
entity |
| Predicate | notablePlayerEast |
P10411
|
FINISHED |
| Object | Allen Iverson |
—
|
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: Allen Iverson | Statement: [2000 NBA All-Star Game, notablePlayerEast, Allen Iverson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerEast Context triple: [2000 NBA All-Star Game, notablePlayerEast, Allen Iverson]
-
A.
notablePlayerEasternConference
chosen
Indicates that a player is recognized as a notable or standout player within the NBA’s Eastern Conference.
-
B.
notableReserveEasternConference
Indicates that an entity is notably recognized as a reserve (non-starting) participant associated with the Eastern Conference in a competitive context.
-
C.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
D.
notableBowlParticipant
Indicates that an entity has participated in a bowl game in a way considered notable or significant.
-
E.
notablePlayerTeam1
Indicates that the referenced player is a notable or prominent member of the first team in a given context or matchup.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: April 27, 2026, 1:33 p.m.