Triple
T36368599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Gator Bowl |
E895691
|
entity |
| Predicate | hasTitleSponsorNameInOfficialTitle |
P145831
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Toyota Gator Bowl, hasTitleSponsorNameInOfficialTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleSponsorNameInOfficialTitle Context triple: [Toyota Gator Bowl, hasTitleSponsorNameInOfficialTitle, true]
-
A.
hasTitleSponsor
Indicates that one entity serves as the primary (title) sponsor for another entity, typically giving its name to the sponsored event, organization, or property.
-
B.
hasTitleSponsorHistorically
Indicates that an entity has served as the primary (title) sponsor of another entity during some period in the past.
-
C.
hasTitleNickname
Indicates that an entity is known by or referred to using a particular title-style nickname.
-
D.
hasGivenNameInTitle
chosen
Indicates that the given name of an entity appears within the title of another entity.
-
E.
hasFullOfficialName
Indicates that an entity is associated with its complete, formally recognized official name.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:10 p.m.