Triple
T9631705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cory Hall |
E232818
|
entity |
| Predicate | partOfCampusArea |
P36352
|
FINISHED |
| Object | engineering quadrant of 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: engineering quadrant of UC Berkeley campus | Statement: [Cory Hall, partOfCampusArea, engineering quadrant of UC Berkeley campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCampusArea Context triple: [Cory Hall, partOfCampusArea, engineering quadrant of UC Berkeley campus]
-
A.
campusArea
Indicates that one entity is the physical area or spatial extent of a campus associated with another entity.
-
B.
isPartOfCampus
chosen
Indicates that one place, facility, or area is located within and belongs to a larger campus.
-
C.
campusAreaType
Indicates the classification of a campus area according to its type or functional category.
-
D.
campusFacility
Indicates that one entity is a facility that is located on or belongs to a particular campus.
-
E.
campusQuadrant
Indicates the specific sector or quadrant of a campus in which an entity is located or to which it belongs.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2621408190bfe2ea5a05359ee0 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.