Triple
T34207810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clippers |
E877561
|
entity |
| Predicate | usesAsMascotBy |
P33791
|
FINISHED |
| Object | University of Maine at Machias |
—
|
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: University of Maine at Machias | Statement: [Clippers, usesAsMascotBy, University of Maine at Machias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAsMascotBy Context triple: [Clippers, usesAsMascotBy, University of Maine at Machias]
-
A.
usesLiveMascot
Indicates that an entity employs a real, living mascot (such as an animal or person) to represent or promote itself.
-
B.
isMascotCounterpartOf
Indicates that one entity serves as the mascot equivalent or counterpart of another entity, typically representing the same thing in a mascot form.
-
C.
hasMascot
Indicates that an entity is represented or symbolized by a particular mascot.
-
D.
usesMascotNameDerivedFrom
Indicates that one entity adopts and uses a mascot whose name is derived from, based on, or inspired by another entity.
-
E.
isMascot
chosen
Indicates that one entity serves as the mascot or symbolic representative for another entity, such as an organization, team, or event.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 1:55 a.m.