Triple
T24259999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1982 MLB All-Star Game |
E604672
|
entity |
| Predicate | hostFranchiseLeague |
P74200
|
FINISHED |
| Object | National League |
—
|
NE NERFINISHED |
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: National League | Statement: [1982 MLB All-Star Game, hostFranchiseLeague, National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostFranchiseLeague Context triple: [1982 MLB All-Star Game, hostFranchiseLeague, National League]
-
A.
hostFranchise
Indicates that one entity serves as the host organization or location for a particular franchise associated with another entity.
-
B.
hostLeague
chosen
Indicates that one entity serves as the organizing league or governing competition framework for another entity, such as a team or event.
-
C.
hostsLeague
Indicates that one entity serves as the organizing or venue-providing host for a particular league.
-
D.
hostsSportsFranchise
Indicates that one entity serves as the home location or base city/venue for a professional sports franchise.
-
E.
hostLeagueOffice
Indicates that an entity serves as the location or venue where a league’s official administrative office is situated.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6656f08190a8140a54eba7c0ce |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.