Triple
T2090796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisville Colonels |
E32663
|
entity |
| Predicate | foundedAsMajorLeagueClub |
P34649
|
FINISHED |
| Object | 1882 |
—
|
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: 1882 | Statement: [Louisville Colonels, foundedAsMajorLeagueClub, 1882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsMajorLeagueClub Context triple: [Louisville Colonels, foundedAsMajorLeagueClub, 1882]
-
A.
establishedInLeague
Indicates that an entity (such as a team or club) was founded or formally created while participating in, or as part of, a particular league.
-
B.
establishedAsCurrentFranchise
Indicates that an entity has been formally designated or recognized as the current active franchise for another entity.
-
C.
foundedAsNHLDivision
Indicates that an NHL division was originally established or created in its initial form as part of the National Hockey League.
-
D.
isOldestClubIn
Indicates that a club is the most ancient or earliest-established club within a specified place or organization.
-
E.
team1Established
Indicates that the first team in a given context has been founded or formally established.
- F. None of above. chosen
Provenance (4 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba7443448190a2642769d0b5fb93 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:43 p.m.