Triple
T22807438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley Hi Country Club |
E564577
|
entity |
| Predicate | usedAsHomeVenueBy |
P53622
|
FINISHED |
| Object | Hornets golf teams |
—
|
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: Hornets golf teams | Statement: [Valley Hi Country Club, usedAsHomeVenueBy, Hornets golf teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsHomeVenueBy Context triple: [Valley Hi Country Club, usedAsHomeVenueBy, Hornets golf teams]
-
A.
homeVenueAlsoUsedBy
chosen
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
B.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
C.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
D.
usedVenuesFrom
Indicates that one entity has made use of or operated in venues associated with another entity.
-
E.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5d41dc819081912d9e29828bfb |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.