Triple
T36129417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB Little League Classic |
E1044973
|
entity |
| Predicate | cityForAssociatedEvent |
P90517
|
FINISHED |
| Object | South Williamsport, Pennsylvania |
—
|
NE NERFINISHED |
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: South Williamsport, Pennsylvania | Statement: [MLB Little League Classic, cityForAssociatedEvent, South Williamsport, Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityForAssociatedEvent Context triple: [MLB Little League Classic, cityForAssociatedEvent, South Williamsport, Pennsylvania]
-
A.
associatedCityEvent
Indicates a relationship where a city is linked to, involved in, or serves as the location for a particular event.
-
B.
cityOfVenue
Indicates the city in which a given venue is located.
-
C.
hostCityOfEvent
chosen
Indicates that a city serves as the location where a particular event is held or takes place.
-
D.
hostCityOfEventParticipatedIn
Indicates that a city is the location where a particular event took place in which an entity participated.
-
E.
cityAssociatedWith
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.