Triple
T38463900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Reign |
E912516
|
entity |
| Predicate | associatedWithTraditionalSportsOwner |
P96897
|
FINISHED |
| Object | Cox Enterprises |
E14655
|
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: Cox Enterprises | Statement: [Atlanta Reign, associatedWithTraditionalSportsOwner, Cox Enterprises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTraditionalSportsOwner Context triple: [Atlanta Reign, associatedWithTraditionalSportsOwner, Cox Enterprises]
-
A.
sportInvolvedInAsOwner
Indicates that an entity has an ownership role in, or is the owner associated with, a particular sport or sports organization.
-
B.
associatedClubOwner
chosen
Indicates that there is an ownership or proprietorship relationship between a club and its associated owner.
-
C.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
D.
sportOwned
Indicates that one entity possesses ownership or control over a particular sport.
-
E.
hasTraditionalSportsAffiliate
Indicates that an entity is formally associated with or linked to a traditional (non-esports) sports organization or team.
- F. None of above.
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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ccb4d9b08190b7896dda59475a35 |
completed | June 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.