Triple
T8858757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dix Stadium |
E210828
|
entity |
| Predicate | distanceFromMainCampusCenter |
P26190
|
FINISHED |
| Object | approximately 3 miles east |
—
|
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: approximately 3 miles east | Statement: [Dix Stadium, distanceFromMainCampusCenter, approximately 3 miles east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromMainCampusCenter Context triple: [Dix Stadium, distanceFromMainCampusCenter, approximately 3 miles east]
-
A.
distanceFromCampusCenter
chosen
Indicates the measured or specified distance between a given location and the central point of the campus.
-
B.
distanceFromChestnutHillCampus
Indicates the spatial distance between a given entity and the Chestnut Hill campus.
-
C.
campusProximity
Indicates that one entity is located near, adjacent to, or within a short distance of a campus associated with the other entity.
-
D.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
E.
campusDistanceBetweenRivals
Indicates the physical distance separating the campuses of two rival institutions.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e536648190ba8da1375478c24f |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.