Triple
T29912657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busch–Livingston Apartments (border area) |
E759708
|
entity |
| Predicate | campusBorder |
P17008
|
FINISHED |
| Object | Busch 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: Busch Campus | Statement: [Busch–Livingston Apartments (border area), campusBorder, Busch Campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusBorder Context triple: [Busch–Livingston Apartments (border area), campusBorder, Busch Campus]
-
A.
campusBorders
chosen
Indicates that the spatial extent or boundary of a campus directly touches, coincides with, or is defined by a given bordering feature or area.
-
B.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
-
C.
campusArea
Indicates that one entity is the physical area or spatial extent of a campus associated with another entity.
-
D.
cityCampus
Indicates that a campus is located within or associated with a particular city.
-
E.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6775b7e54819083176ce918b32eec |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:11 p.m.