Triple
T34355348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellis Avenue |
E881704
|
entity |
| Predicate | hasCampusBuildingsAlong |
P2465
|
FINISHED |
| Object | University of Chicago academic buildings |
—
|
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: University of Chicago academic buildings | Statement: [Ellis Avenue, hasCampusBuildingsAlong, University of Chicago academic buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampusBuildingsAlong Context triple: [Ellis Avenue, hasCampusBuildingsAlong, University of Chicago academic buildings]
-
A.
hasCampusOn
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
B.
hasUniversityBuilding
Indicates that a university possesses, controls, or includes a specific building as part of its physical infrastructure.
-
C.
hasCampusFeature
chosen
Indicates that a campus possesses or includes a specific physical or functional feature.
-
D.
hasMainBuildings
Indicates that one entity possesses or is associated with one or more primary or principal buildings.
-
E.
hasCampusCity
Indicates that an educational institution or campus is located in a particular city.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 1, 2026, 1:58 a.m.