Triple
T16433429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancaster JetHawks |
E399122
|
entity |
| Predicate | successorUseOfBallpark |
P122768
|
FINISHED |
| Object | independent and amateur events after 2020 |
—
|
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: independent and amateur events after 2020 | Statement: [Lancaster JetHawks, successorUseOfBallpark, independent and amateur events after 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorUseOfBallpark Context triple: [Lancaster JetHawks, successorUseOfBallpark, independent and amateur events after 2020]
-
A.
successorBallpark
Indicates that one ballpark directly replaces another as the subsequent venue for a team or event.
-
B.
successorTeamAtBallpark
Indicates that one team is the direct successor of another as the primary tenant or home team at a particular ballpark.
-
C.
formerBallpark
Indicates that a location previously served as a ballpark but no longer functions in that role.
-
D.
homeBallparkSubsequentName
Indicates that a team's home ballpark later became known by a different name.
-
E.
ballparkFormerName
Indicates that one name was previously used as the official name of a particular ballpark before it was changed.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba01a1c8190b5a4700e2364ae63 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.