Triple
T32009068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn State Nittany Lions rugby |
E817348
|
entity |
| Predicate | associatedUniversityMascot |
P44175
|
FINISHED |
| Object | Nittany Lion |
E198759
|
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: Nittany Lion | Statement: [Penn State Nittany Lions rugby, associatedUniversityMascot, Nittany Lion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedUniversityMascot Context triple: [Penn State Nittany Lions rugby, associatedUniversityMascot, Nittany Lion]
-
A.
universityMascot
chosen
Indicates that one entity serves as the official mascot representing a particular university.
-
B.
mascotOfHighSchool
Indicates that one entity serves as the official mascot representing a particular high school.
-
C.
isMascotCounterpartOf
Indicates that one entity serves as the mascot equivalent or counterpart of another entity, typically representing the same thing in a mascot form.
-
D.
mascotForSportLevel
Indicates that an entity serves as the mascot specifically for a given sport at a particular competitive or organizational level.
-
E.
mascotName
Indicates the name assigned to a mascot that represents an entity.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eddd50d008190adef55c6376dfe7c |
completed | June 14, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:15 a.m.