Triple
T27546414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 NBA All-Star Game |
E695373
|
entity |
| Predicate | notablePlayerWest |
P10412
|
FINISHED |
| Object | Kobe Bryant |
—
|
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: Kobe Bryant | Statement: [2000 NBA All-Star Game, notablePlayerWest, Kobe Bryant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerWest Context triple: [2000 NBA All-Star Game, notablePlayerWest, Kobe Bryant]
-
A.
notablePlayerWesternConference
chosen
Indicates that a player is recognized as a notable or standout player within the NBA’s Western Conference.
-
B.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
C.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
-
D.
organNotablePlayer
Indicates that a person is a notable or distinguished player of a particular organ.
-
E.
notableBowlParticipant
Indicates that an entity has participated in a bowl game in a way considered notable or significant.
- 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_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
Created at: April 27, 2026, 1:33 p.m.