Triple
T36783311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Mets executive |
E908832
|
entity |
| Predicate | worksInSport |
P39137
|
FINISHED |
| Object | baseball |
—
|
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: baseball | Statement: [New York Mets executive, worksInSport, baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksInSport Context triple: [New York Mets executive, worksInSport, baseball]
-
A.
sportDepictedInWork
Indicates that a particular sport is represented or shown within a creative or informational work (such as a book, film, artwork, or game).
-
B.
performsAtSport
Indicates that an entity carries out or participates in an activity at a particular sport or sporting context.
-
C.
worksInLeague
Indicates that an organization, team, or individual operates, competes, or participates within a specified league.
-
D.
basedInSport
chosen
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
E.
eraOfSport
Indicates the historical period or era during which a particular sport, sporting event, or athlete is primarily associated or took place.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.