Triple
T38435966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 Eastern Conference |
E903941
|
entity |
| Predicate | finalsRepresentative |
P43077
|
FINISHED |
| Object | Detroit Shock |
—
|
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: Detroit Shock | Statement: [2003 Eastern Conference, finalsRepresentative, Detroit Shock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalsRepresentative Context triple: [2003 Eastern Conference, finalsRepresentative, Detroit Shock]
-
A.
representsFinals
Indicates that one entity serves as the final or culminating stage, outcome, or version of another entity.
-
B.
representativeDetermined
chosen
Indicates that an official representative has been identified and designated for a particular entity or context.
-
C.
winnerRepresents
Indicates that the winner of a competition or contest serves as a representative for a particular group, organization, or entity.
-
D.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
-
E.
finalists
Indicates that the related entities have advanced to the final round or stage of a competition, selection process, or evaluation.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 3, 2026, 4:31 p.m.