Triple
T4168184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League All-Star |
E84493
|
entity |
| Predicate | locationTypeOfEvent |
P17057
|
FINISHED |
| Object | rotating MLB ballparks |
—
|
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: rotating MLB ballparks | Statement: [National League All-Star, locationTypeOfEvent, rotating MLB ballparks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationTypeOfEvent Context triple: [National League All-Star, locationTypeOfEvent, rotating MLB ballparks]
-
A.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
B.
sponsorLocation
Indicates that an entity acts as a sponsor for activities, events, or operations occurring at a specified location.
-
C.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
D.
cityOfVenue
Indicates the city in which a given venue is located.
-
E.
typicallyHeldIn
chosen
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02c573788190a60ab3f83b07a6f6 |
completed | March 9, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.