Triple
T3070979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midsummer Classic |
E64019
|
entity |
| Predicate | rotatingHost |
P13981
|
FINISHED |
| Object | MLB cities |
—
|
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: MLB cities | Statement: [Midsummer Classic, rotatingHost, MLB cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotatingHost Context triple: [Midsummer Classic, rotatingHost, MLB cities]
-
A.
typicalHostRotation
Indicates that an entity normally or characteristically serves as the rotational host or primary environment in which another entity operates or resides.
-
B.
rotatingHostCity
chosen
Indicates that the role of host city changes periodically among different cities according to a rotation schedule.
-
C.
alternatingHost
Indicates a relationship where two or more entities take turns serving as host in a recurring or cyclical manner.
-
D.
rotatesAmong
Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
-
E.
rotatingLocation
Indicates that an entity is rotating around, or undergoing rotational motion at, a specified location or point in space.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14b366881908e2ca104e5f38251 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.