Triple
T31752065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas League championship 2000 |
E810448
|
entity |
| Predicate | hasChampionTeamLevel |
P155910
|
FINISHED |
| Object | Minor 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: Minor League Baseball team | Statement: [Texas League championship 2000, hasChampionTeamLevel, Minor League Baseball team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionTeamLevel Context triple: [Texas League championship 2000, hasChampionTeamLevel, Minor League Baseball team]
-
A.
hadChampionTeam
chosen
Indicates that an entity (such as a league, season, or competition) had a specific team recognized as its champion.
-
B.
hasChampionClass
Indicates that an entity is associated with, or belongs to, a particular champion class or category.
-
C.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
D.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
E.
hasCurrentTeam
Indicates that an entity is presently a member of or affiliated with a specific team.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 30, 2026, 11:28 p.m.