Triple
T38366542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer League All-Star Game |
E892460
|
entity |
| Predicate | hasHostTeam |
P2700
|
FINISHED |
| Object | Billings Mustangs |
—
|
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: Billings Mustangs | Statement: [Pioneer League All-Star Game, hasHostTeam, Billings Mustangs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostTeam Context triple: [Pioneer League All-Star Game, hasHostTeam, Billings Mustangs]
-
A.
hasHostStadiumTeam
Indicates that a particular team is the primary host or home team for events held at a given stadium.
-
B.
hostTeam
chosen
Indicates that one team serves as the host (home) team in relation to a particular game, match, or event.
-
C.
hasHostNation
Indicates that one entity serves as the host nation for another entity, such as an event, organization, or activity.
-
D.
hasHomeTeamType
Indicates that an entity has a specified classification or category for its home team (e.g., type or role of the home team in a competition).
-
E.
finalHostTeam
Indicates that a team is designated as the host team for the final match or final stage of a competition.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:31 p.m.