Triple
T23843918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duffy’s Cliff |
E591066
|
entity |
| Predicate | homeBallparkEra |
P154158
|
FINISHED |
| Object | pre-Fenway Park era |
—
|
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: pre-Fenway Park era | Statement: [Duffy’s Cliff, homeBallparkEra, pre-Fenway Park era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeBallparkEra Context triple: [Duffy’s Cliff, homeBallparkEra, pre-Fenway Park era]
-
A.
homeBallparkDuringNicknameEra
Indicates that a particular ballpark served as the team's home field during the specific time period associated with a given nickname era.
-
B.
homeBallparkEmphasis
Indicates an emphasis or special significance placed on a team's home ballpark in the context of a relationship or event.
-
C.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
D.
homeBallparkOfChampion
Indicates that a particular ballpark serves as the home stadium for a championship-winning team or champion.
-
E.
homeBallparkSubsequentName
Indicates that a team's home ballpark later became known by a different name.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c8898a0c8190b4d55852fc30260f |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:09 p.m.