Triple
T26510797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UW East Campus |
E669675
|
entity |
| Predicate | campusPlanningAreaOf |
P1243
|
FINISHED |
| Object | University of Washington Seattle campus |
—
|
NE NERFINISHED |
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 of Washington Seattle campus | Statement: [UW East Campus, campusPlanningAreaOf, University of Washington Seattle campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusPlanningAreaOf Context triple: [UW East Campus, campusPlanningAreaOf, University of Washington Seattle campus]
-
A.
campusArea
chosen
Indicates that one entity is the physical area or spatial extent of a campus associated with another entity.
-
B.
campusAreaType
Indicates the classification of a campus area according to its type or functional category.
-
C.
campusSector
Indicates that one location or facility is part of, or belongs to, a specific sector or zone within a campus.
-
D.
hasUniversityCampusArea
Indicates the total physical area occupied by a university’s campus.
-
E.
campusDesignation
Indicates the formal classification or status assigned to a particular campus within an institution or system.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61391ca58819093a6561a9c4ae670 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:20 a.m.