Triple
T623056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peach Bowl |
E14554
|
entity |
| Predicate | roleInCFP |
P6124
|
FINISHED |
| Object | rotating semifinal host |
—
|
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 semifinal host | Statement: [Peach Bowl, roleInCFP, rotating semifinal host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCFP Context triple: [Peach Bowl, roleInCFP, rotating semifinal host]
-
A.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
roleInvolves
chosen
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
conferenceAffiliation
Indicates that an entity is formally associated with or participates in a particular conference (e.g., as an organizer, sponsor, or member).
-
D.
conference2
Indicates that one entity is a conference or event that is associated with, hosted by, or otherwise related to another entity.
-
E.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e41753881909f0faed720cc31bc |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.