Triple
T9332880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Circle (UC Berkeley) |
E224566
|
entity |
| Predicate | positionOnCampus |
P87563
|
FINISHED |
| Object | western edge of the UC Berkeley campus |
—
|
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: western edge of the UC Berkeley campus | Statement: [West Circle (UC Berkeley), positionOnCampus, western edge of the UC Berkeley campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCampus Context triple: [West Circle (UC Berkeley), positionOnCampus, western edge of the UC Berkeley campus]
-
A.
campusLandmark
Indicates that something serves as a notable or recognizable landmark located on or associated with a campus.
-
B.
campusArea
Indicates that one entity is the physical area or spatial extent of a campus associated with another entity.
-
C.
cityCampusServes
Indicates that a city campus provides services, resources, or support to a particular population, area, or institution.
-
D.
cityCampus
Indicates that a campus is located within or associated with a particular city.
-
E.
campusDistribution
Indicates how resources, activities, or populations are allocated or spread across different campuses within an institution.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37ecfd9481908b54e3d4187fb0ce |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:39 p.m.