Triple
T27304697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn State Greater Allegheny |
E689017
|
entity |
| Predicate | campusNameHistory |
P138798
|
FINISHED |
| Object | formerly known as Penn State McKeesport |
—
|
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: formerly known as Penn State McKeesport | Statement: [Penn State Greater Allegheny, campusNameHistory, formerly known as Penn State McKeesport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusNameHistory Context triple: [Penn State Greater Allegheny, campusNameHistory, formerly known as Penn State McKeesport]
-
A.
historicalNameOfInstitution
chosen
Indicates that one institution is a former or historical name by which another institution was previously known.
-
B.
campusNameOrigin
Indicates the source or reason behind how a campus received its name.
-
C.
universityFormerName
Indicates that a university previously had a different official name before adopting its current one.
-
D.
campusName
Indicates the official name assigned to a particular campus.
-
E.
isHistoricCampus
Indicates that a campus has historical significance or heritage status, often due to its age, architecture, or role in past events.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6278777188190aa2e58c900c21662 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:24 a.m.