Triple
T7155696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alumni Pool vicinity |
E166805
|
entity |
| Predicate | nearbyFacilityType |
P75188
|
FINISHED |
| Object | athletic facilities |
—
|
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: athletic facilities | Statement: [Alumni Pool vicinity, nearbyFacilityType, athletic facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyFacilityType Context triple: [Alumni Pool vicinity, nearbyFacilityType, athletic facilities]
-
A.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
B.
nearbyVenue
Indicates that one venue is located close to another venue in physical space.
-
C.
findingOnFacilities
Indicates a relationship where an inspection or assessment identifies a specific issue, observation, or result associated with particular facilities.
-
D.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- F. None of above. chosen
Provenance (4 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80dafdc8190b24863b83f084d12 |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:47 p.m.