Triple
T159773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lerner family |
E3256
|
entity |
| Predicate | sportsFranchiseOwnership |
P2617
|
FINISHED |
| Object | Major League Baseball team |
—
|
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: Major League Baseball team | Statement: [Lerner family, sportsFranchiseOwnership, Major League Baseball team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportsFranchiseOwnership Context triple: [Lerner family, sportsFranchiseOwnership, Major League Baseball team]
-
A.
acquiredSportsTeam
chosen
Indicates that one entity has purchased and taken ownership of a sports team from another party.
-
B.
sportOwned
Indicates that one entity possesses ownership or control over a particular sport.
-
C.
team1Franchise
Indicates that an entity serves as or represents the franchise associated with the first team in a given sports or competitive context.
-
D.
league
Indicates that an organization or team participates in, is a member of, or is associated with a particular sports or competitive league.
-
E.
sponsorSport
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.