Triple
T18435997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carter–Finley Stadium |
E450391
|
entity |
| Predicate | distanceFromCampus |
P68402
|
FINISHED |
| Object | adjacent to NC State main 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: adjacent to NC State main campus | Statement: [Carter–Finley Stadium, distanceFromCampus, adjacent to NC State main campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromCampus Context triple: [Carter–Finley Stadium, distanceFromCampus, adjacent to NC State main campus]
-
A.
distanceFromCampusCenter
Indicates the measured or specified distance between a given location and the central point of the campus.
-
B.
campusProximity
chosen
Indicates that one entity is located near, adjacent to, or within a short distance of a campus associated with the other entity.
-
C.
adjacentToCampusOf
Indicates that one entity is located next to or directly bordering the campus area of another entity.
-
D.
distanceFromChestnutHillCampus
Indicates the spatial distance between a given entity and the Chestnut Hill campus.
-
E.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0cd30c8190b8417c264e60d3a5 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:28 a.m.