Triple
T11818891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Volunteers softball |
E281072
|
entity |
| Predicate | homeFacilityUse |
P101666
|
FINISHED |
| Object | on-campus stadium |
—
|
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: on-campus stadium | Statement: [Tennessee Volunteers softball, homeFacilityUse, on-campus stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFacilityUse Context triple: [Tennessee Volunteers softball, homeFacilityUse, on-campus stadium]
-
A.
homeFacilityName
Indicates the name of the primary facility or location that serves as the entity’s designated home base.
-
B.
userFacility
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
-
C.
housesFacility
Indicates that one entity serves as a location or container in which the other entity (a facility) is situated or operates.
-
D.
homeFacilityCity
Indicates the city in which an entity’s primary or home facility is located.
-
E.
facility
Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e760988190b50d13bba5ef5b43 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.