Triple
T19572947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eden Hall Campus |
E489768
|
entity |
| Predicate | primaryAcademicUse |
P778
|
FINISHED |
| Object | sustainability studies |
—
|
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: sustainability studies | Statement: [Eden Hall Campus, primaryAcademicUse, sustainability studies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAcademicUse Context triple: [Eden Hall Campus, primaryAcademicUse, sustainability studies]
-
A.
academicUse
Indicates that something is intended for, suitable for, or used within an academic or educational context.
-
B.
academicFocus
chosen
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
-
C.
academicAccess
Indicates that one entity has permission or the ability to use, enter, or benefit from academic resources, environments, or services provided by another entity.
-
D.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
-
E.
primarySubjectArea
Indicates the main academic or topical field to which something (such as a work, course, or resource) is most centrally related.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402228488190b5649d4bbd34d019 |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.