Triple
T26876136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Tech Yellow Jackets |
E676752
|
entity |
| Predicate | hasSpiritSquad |
P102803
|
FINISHED |
| Object | Georgia Tech band |
—
|
NE NERFINISHED |
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: Georgia Tech band | Statement: [Georgia Tech Yellow Jackets, hasSpiritSquad, Georgia Tech band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpiritSquad Context triple: [Georgia Tech Yellow Jackets, hasSpiritSquad, Georgia Tech band]
-
A.
hasHeroTeam
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
-
B.
isEliteSquad
Indicates that a group or unit is recognized as a top-tier, highly skilled, and specially selected squad within a larger organization or force.
-
C.
hasTeamFor
chosen
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
D.
hasSubteam
Indicates that one team is a subordinate or component team within another, larger team.
-
E.
wasInSquadFor
Indicates that an individual was a member of a particular squad or team, typically for a specific event, period, or organization.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 5:36 a.m.