Triple
T32365816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nittany Nation |
E826986
|
entity |
| Predicate | fanSectionFor |
P24482
|
FINISHED |
| Object | home games |
—
|
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: home games | Statement: [Nittany Nation, fanSectionFor, home games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanSectionFor Context triple: [Nittany Nation, fanSectionFor, home games]
-
A.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
B.
fanSectionEndline
Indicates the boundary line or area at the end of a fan-designated section, marking where that fan section terminates.
-
C.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
D.
fanBase1
Indicates that one entity serves as the primary or original fan base supporting another entity.
-
E.
fanSectionLocation
chosen
Indicates the specific area or section within a venue where a fan or group of fans is located.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9db42c819094f2f94d10dfd3e4 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:50 a.m.