Triple
T4716812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Mara |
E104661
|
entity |
| Predicate | teamOwnershipRole |
P59138
|
FINISHED |
| Object | co-owner |
—
|
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: co-owner | Statement: [John Mara, teamOwnershipRole, co-owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamOwnershipRole Context triple: [John Mara, teamOwnershipRole, co-owner]
-
A.
teamOwnershipModel
Indicates the type or structure of ownership relationship that exists between a team and its owning entity (such as an individual, group, or organization).
-
B.
teamOwner
Indicates that one entity holds ownership or controlling stake over a team.
-
C.
memberOfSportsTeamOwnershipGroup
Indicates that an entity is part of the ownership group that owns or controls a sports team.
-
D.
leagueAffiliationThroughOwnedTeam
Indicates that an entity is affiliated with a league by virtue of owning a team that participates in that league.
-
E.
governingBodyOfOwnedTeam
Indicates that one entity serves as the governing or managing body responsible for overseeing and controlling the operations of a team that it owns.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd680b06e881908de87edf815f3cc0 |
completed | March 20, 2026, 3:30 p.m. |
Created at: March 20, 2026, 1:18 p.m.