Triple
T17336619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilitch family |
E420951
|
entity |
| Predicate | sportsOwnershipStart |
P127069
|
FINISHED |
| Object | Detroit Red Wings purchased in 1982 |
—
|
LITERAL 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: Detroit Red Wings purchased in 1982 | Statement: [Ilitch family, sportsOwnershipStart, Detroit Red Wings purchased in 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsOwnershipStart Context triple: [Ilitch family, sportsOwnershipStart, Detroit Red Wings purchased in 1982]
-
A.
sportsOwnershipArea
Indicates the geographic area or region over which a sports organization, team, or owner holds ownership or territorial rights.
-
B.
sportOwnershipArea
Indicates the geographic area or region over which a particular sport organization, team, or entity holds ownership or control rights.
-
C.
sportOwned
Indicates that one entity possesses ownership or control over a particular sport.
-
D.
sportInvolvedInAsOwner
Indicates that an entity has an ownership role in, or is the owner associated with, a particular sport or sports organization.
-
E.
sportsTeamOwned
Indicates that one entity is the owner (or part-owner) of a sports team entity.
- F. None of above. chosen
Provenance (4 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a121aa081908a62fa59d3d28765 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.