Triple
T37506709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Illinois Panthers volleyball games |
E932111
|
entity |
| Predicate | featureMascot |
P84914
|
FINISHED |
| Object | Billy the Panther |
E273445
|
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: Billy the Panther | Statement: [Eastern Illinois Panthers volleyball games, featureMascot, Billy the Panther]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureMascot Context triple: [Eastern Illinois Panthers volleyball games, featureMascot, Billy the Panther]
-
A.
mascotCharacteristic
Indicates that a mascot possesses or is associated with a particular characteristic or trait.
-
B.
hasMascotFeature
chosen
Indicates that an entity possesses a specific characteristic, attribute, or element related to a mascot.
-
C.
typeOfMascot
Indicates that one entity is a mascot and specifies the category or kind of mascot it is (e.g., animal, human, object, etc.).
-
D.
mascotTheme
Indicates that an entity serves as the representative mascot associated with a particular theme, concept, or style.
-
E.
coMascot
Indicates that two entities serve together as mascots for the same organization, event, or group.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409efb44b0819085eb18ac4ae3ad16 |
completed | June 28, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.