Triple
T9777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Libraries |
E197
|
entity |
| Predicate | hasAudience |
P793
|
FINISHED |
| Object | university community |
—
|
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: university community | Statement: [Penn Libraries, hasAudience, university community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudience Context triple: [Penn Libraries, hasAudience, university community]
-
A.
hasNotableBearer
Indicates that an entity (such as a name, title, or identifier) is borne by at least one notable person or entity.
-
B.
hasRepresentationIn
Indicates that one entity is represented, depicted, or encoded within another entity, such as a concept, object, or data structure having a corresponding representation in a specific medium or context.
-
C.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
D.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
-
E.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
- F. None of above. chosen
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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a240b249788190af8dbf7e80e9c91b |
completed | Feb. 28, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69a23fe52ec48190a4d24101c91434ed |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a240b1551c81908abcae128ea45d00 |
completed | Feb. 28, 2026, 1:11 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.