Triple
T34473765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International League East Division |
E884974
|
entity |
| Predicate | ballparksLocationRegion |
P178988
|
FINISHED |
| Object | NortheasternUnitedStates |
—
|
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: NortheasternUnitedStates | Statement: [International League East Division, ballparksLocationRegion, NortheasternUnitedStates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballparksLocationRegion Context triple: [International League East Division, ballparksLocationRegion, NortheasternUnitedStates]
-
A.
ballparks
Indicates that one entity makes an approximate estimate or rough guess about another entity or quantity.
-
B.
ballparkLocatedOn
Indicates that a ballpark is situated on or directly associated with a specific street, road, or thoroughfare.
-
C.
ballparkCity
Indicates that a ballpark is located in a particular city.
-
D.
ballparkState
Indicates the current condition or status of a ballpark, such as whether it is open, closed, under maintenance, or in another operational state.
-
E.
ballparkAlsoKnownAs
Indicates that a ballpark is referred to by an alternative name or alias.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2:01 a.m.