Triple
T31914546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagner Seahawks |
E814789
|
entity |
| Predicate | usesMascotIn |
P52
|
FINISHED |
| Object | collegiate sports competitions |
—
|
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: collegiate sports competitions | Statement: [Wagner Seahawks, usesMascotIn, collegiate sports competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMascotIn Context triple: [Wagner Seahawks, usesMascotIn, collegiate sports competitions]
-
A.
usesLiveMascot
Indicates that an entity employs a real, living mascot (such as an animal or person) to represent or promote itself.
-
B.
hasMascot
chosen
Indicates that an entity is represented or symbolized by a particular mascot.
-
C.
isMascot
Indicates that one entity serves as the mascot or symbolic representative for another entity, such as an organization, team, or event.
-
D.
usesMascotNameDerivedFrom
Indicates that one entity adopts and uses a mascot whose name is derived from, based on, or inspired by another entity.
-
E.
hasMascotIdentity
Indicates that an entity serves as or possesses the role/identity of a mascot for another entity.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 12:02 a.m.