Triple
T38435901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 WNBA Finals |
E903939
|
entity |
| Predicate | notablePlayerDetroitShock |
P204653
|
FINISHED |
| Object | Deanna Nolan |
E731585
|
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: Deanna Nolan | Statement: [2006 WNBA Finals, notablePlayerDetroitShock, Deanna Nolan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerDetroitShock Context triple: [2006 WNBA Finals, notablePlayerDetroitShock, Deanna Nolan]
-
A.
notableAlumnusInNBA
Indicates that a person is a distinguished former student of an institution who has gone on to play in the NBA.
-
B.
notableUndraftedPlayer
Indicates that a player is recognized for significant achievements or impact despite not having been selected in a professional league draft.
-
C.
notablePlayerWarriors
Indicates that a person is a notable or prominent player for the Golden State Warriors basketball team.
-
D.
notablePlayerEasternConference
Indicates that a player is recognized as a notable or standout player within the NBA’s Eastern Conference.
-
E.
notablePlayerWesternConference
Indicates that a player is recognized as a notable or standout player within the NBA’s Western Conference.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a7b845e6d108190af030f1cb5a06bea |
completed | Aug. 11, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.