Triple
T13267427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Exposition and State Fair |
E315957
|
entity |
| Predicate | hasVenueFeature |
P55865
|
FINISHED |
| Object | racetrack |
—
|
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: racetrack | Statement: [California Exposition and State Fair, hasVenueFeature, racetrack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVenueFeature Context triple: [California Exposition and State Fair, hasVenueFeature, racetrack]
-
A.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
B.
hasVenueFunction
chosen
Indicates that a venue serves a particular function or role (such as hosting events, performances, or specific activities).
-
C.
hasVenueContext
Indicates that an entity is associated with a particular venue or setting that provides contextual information about where it occurs or is situated.
-
D.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
E.
hasAttachedVenue
Indicates that one entity has another entity linked or associated with it as a venue.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:25 p.m.