Triple
T36981051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 Western Conference Finals |
E914828
|
entity |
| Predicate | team2StarPlayer |
P186849
|
FINISHED |
| Object | Chris Webber |
E102935
|
NE 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: Chris Webber | Statement: [2002 Western Conference Finals, team2StarPlayer, Chris Webber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2StarPlayer Context triple: [2002 Western Conference Finals, team2StarPlayer, Chris Webber]
-
A.
managerTeam1
Indicates that an entity serves as the manager or leader of a specific team (team1) within an organization.
-
B.
featuresPlayersFrom
Indicates that something (such as a work, event, or production) includes or showcases players originating from a specified source, group, or location.
-
C.
team2
Indicates that the second team involved in a competitive or collaborative context is associated with a given entity or event.
-
D.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
-
E.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
- F. None of above. chosen
Provenance (5 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c4e48748190a562e6973d789802 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.