Triple
T33697751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad Dobler |
E863360
|
entity |
| Predicate | playedYearsForStLouisCardinals |
P186486
|
FINISHED |
| Object | 1972–1977 |
—
|
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: 1972–1977 | Statement: [Conrad Dobler, playedYearsForStLouisCardinals, 1972–1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedYearsForStLouisCardinals Context triple: [Conrad Dobler, playedYearsForStLouisCardinals, 1972–1977]
-
A.
establishedAsStLouisCardinals
Indicates that an entity was formally founded, designated, or recognized as the St. Louis Cardinals organization or team.
-
B.
activeYearsMLB
Indicates the span of years during which an entity was actively participating in Major League Baseball.
-
C.
teamNumberWithStLouisCardinals
Indicates that the entity is associated with a team number specifically for the St. Louis Cardinals organization.
-
D.
endedAsStLouisCardinals
Indicates that an entity’s tenure, career, or existence concluded while it was associated with or known as the St. Louis Cardinals.
-
E.
StLouisCardinalsLeague
Indicates the league in which the St. Louis Cardinals baseball team competes.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 1, 2026, 1:43 a.m.