Triple
T25586813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Cardinals |
E641406
|
entity |
| Predicate | hasParentMLBClub |
P71726
|
FINISHED |
| Object | St. Louis Cardinals |
—
|
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: St. Louis Cardinals | Statement: [Springfield Cardinals, hasParentMLBClub, St. Louis Cardinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentMLBClub Context triple: [Springfield Cardinals, hasParentMLBClub, St. Louis Cardinals]
-
A.
hasFatherTeamAssociation
Indicates a relationship where an entity is associated with a team through or by virtue of its father’s team affiliation.
-
B.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
-
C.
majorLeagueParentClub
chosen
Indicates that one sports club serves as the primary or top-tier (major league) affiliate or parent organization of another club.
-
D.
hasParentFranchise
Indicates that one franchise entity is the parent or overarching franchise of another franchise entity.
-
E.
affiliatedClubOf
Indicates that one entity is a club with which another entity is formally associated or connected.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 4:17 p.m.