Triple
T29990873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSU Vikings |
E761873
|
entity |
| Predicate | fencingFacility |
P90223
|
FINISHED |
| Object | Woodling Gymnasium |
—
|
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: Woodling Gymnasium | Statement: [CSU Vikings, fencingFacility, Woodling Gymnasium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fencingFacility Context triple: [CSU Vikings, fencingFacility, Woodling Gymnasium]
-
A.
homeFencingVenue
chosen
Indicates that a specified venue serves as the primary or regular location where an entity (such as a team or fencer) hosts its fencing activities or events.
-
B.
sportsFacility
Indicates that one entity is a sports facility where sports or physical activities can take place for the other entity.
-
C.
gymnasticsArena
Indicates that one entity serves as a gymnastics arena or venue where gymnastics activities, events, or competitions take place in relation to another entity.
-
D.
trainingFacilityLocation
Indicates the place or site where a training facility is situated or operates.
-
E.
isOutdoorFacility
Indicates that a facility is located outdoors or primarily functions in an open-air environment.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791aa82c8190afb7c808cddbf46a |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:38 p.m.