Triple
T38079862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia vs. Georgia Tech |
E950820
|
entity |
| Predicate | associatedWithMascotTeam2 |
P52
|
FINISHED |
| Object | Buzz |
E172176
|
NE 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: Buzz | Statement: [Georgia vs. Georgia Tech, associatedWithMascotTeam2, Buzz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMascotTeam2 Context triple: [Georgia vs. Georgia Tech, associatedWithMascotTeam2, Buzz]
-
A.
isMascotCounterpartOf
Indicates that one entity serves as the mascot equivalent or counterpart of another entity, typically representing the same thing in a mascot form.
-
B.
hasCompanionMascot
Indicates that an entity is accompanied by or associated with a specific mascot serving as its companion.
-
C.
hasMascot
chosen
Indicates that an entity is represented or symbolized by a particular mascot.
-
D.
hasSiblingMascot
Indicates that one mascot is a sibling (e.g., brother or sister) of another mascot.
-
E.
mascotCollectiveName
Indicates that a mascot is associated with and represents a particular collective group, organization, or team name.
- F. None of above.
Provenance (4 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d4a1820819099b04a1a6c03c34a |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.