Triple
T33056157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Steps |
E845849
|
entity |
| Predicate | roleInCampusLife |
P29527
|
FINISHED |
| Object | informal study space |
—
|
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: informal study space | Statement: [Low Steps, roleInCampusLife, informal study space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCampusLife Context triple: [Low Steps, roleInCampusLife, informal study space]
-
A.
campusLife
chosen
Indicates the overall experience, activities, and social environment associated with being part of a particular campus or educational institution.
-
B.
campusRole
Indicates the specific position, function, or capacity an individual holds within a campus or academic institution.
-
C.
roleWithinCollege
Indicates the specific position, function, or capacity an entity holds within a particular college.
-
D.
campusScope
Indicates that the relationship, condition, or rule applies specifically within the boundaries or context of a particular campus.
-
E.
campusFocus
Indicates that something (such as a program, initiative, or activity) is specifically oriented toward or centered on a particular campus.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: May 1, 2026, 1:25 a.m.