Triple
T22960293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rick Schnall |
E570875
|
entity |
| Predicate | teamAcquisitionInvolved |
P150393
|
FINISHED |
| Object | Charlotte Hornets ownership stake |
—
|
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: Charlotte Hornets ownership stake | Statement: [Rick Schnall, teamAcquisitionInvolved, Charlotte Hornets ownership stake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamAcquisitionInvolved Context triple: [Rick Schnall, teamAcquisitionInvolved, Charlotte Hornets ownership stake]
-
A.
acquiredSportsTeam
Indicates that one entity has purchased and taken ownership of a sports team from another party.
-
B.
acquiredTeamNameAtPurchase
Indicates that an entity obtained ownership of a team, identified by its name, at the time of purchase.
-
C.
tradeToTeam
Indicates the action of transferring a player or asset from one team to another team via a trade.
-
D.
acquiredPlayersFrom
Indicates that one entity obtained players from another entity, typically through a transfer, trade, or purchase.
-
E.
teamAbsorbed
Indicates that one team is taken over, merged into, or incorporated by another team, ceasing to exist as an independent 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f3c96081909abd6ec32103d4c3 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:47 p.m.