Triple
T37612119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Washington Eagles |
E935809
|
entity |
| Predicate | homeFacilityForSwimming |
P118138
|
FINISHED |
| Object | Goolrick Hall pool |
—
|
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: Goolrick Hall pool | Statement: [Mary Washington Eagles, homeFacilityForSwimming, Goolrick Hall pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFacilityForSwimming Context triple: [Mary Washington Eagles, homeFacilityForSwimming, Goolrick Hall pool]
-
A.
hasSwimmingAreaType
Indicates that an entity’s swimming area is classified as a specific type or category (e.g., indoor pool, open water, designated beach zone).
-
B.
homeAquaticsVenue
chosen
Indicates that a venue serves as the primary location where an entity regularly conducts its aquatic-related activities or events.
-
C.
openWaterSwimmingVenue
Indicates that a location serves as a venue where open water swimming activities or events take place.
-
D.
swimmingAllowed
Indicates that swimming is permitted at a particular place, time, or under specified conditions.
-
E.
hasSwimmingPool
Indicates that the subject possesses or includes a swimming pool as one of its features.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.