Triple
T37620304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmetto Bowl |
E936048
|
entity |
| Predicate | homeVenueRotation |
P100280
|
FINISHED |
| Object | alternating between Clemson and Columbia |
—
|
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: alternating between Clemson and Columbia | Statement: [Palmetto Bowl, homeVenueRotation, alternating between Clemson and Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueRotation Context triple: [Palmetto Bowl, homeVenueRotation, alternating between Clemson and Columbia]
-
A.
rotatingVenue
Indicates that an event or activity takes place at different venues over time, rather than being fixed to a single location.
-
B.
homeVenueFocus
Indicates a primary or central emphasis on a particular venue as the main location associated with an entity’s activities or presence.
-
C.
homeVenueAlternatesBetween
chosen
Indicates that the designated home venue for an entity regularly switches between two or more locations according to some pattern or schedule.
-
D.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
-
E.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.