Triple
T25586811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Cardinals |
E641406
|
entity |
| Predicate | hasMiLBClassification |
P40951
|
FINISHED |
| Object | Double-A |
—
|
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: Double-A | Statement: [Springfield Cardinals, hasMiLBClassification, Double-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMiLBClassification Context triple: [Springfield Cardinals, hasMiLBClassification, Double-A]
-
A.
isOfficiallyRecognizedByMLB
Indicates that Major League Baseball formally acknowledges or sanctions the entity as meeting its official standards or status.
-
B.
hasMLBTeamID
Indicates that an entity is associated with a specific Major League Baseball (MLB) team identifier.
-
C.
hasMinorLeagueStatus
chosen
Indicates that an entity holds a classification or designation as belonging to a minor league level within a hierarchical league system.
-
D.
hasRelativeInMLB
Indicates that one person has a family member who plays or has played in Major League Baseball (MLB).
-
E.
hasMinorLeagueSport
Indicates that a location or organization hosts, supports, or is associated with a minor league sports team or 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 4:17 p.m.