Triple
T30973241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodwood Festival of Speed |
E789156
|
entity |
| Predicate | mainVenueFeature |
P166905
|
FINISHED |
| Object | Goodwood Hillclimb |
—
|
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: Goodwood Hillclimb | Statement: [Goodwood Festival of Speed, mainVenueFeature, Goodwood Hillclimb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainVenueFeature Context triple: [Goodwood Festival of Speed, mainVenueFeature, Goodwood Hillclimb]
-
A.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
B.
homeVenueIncludes
Indicates that a specified venue is part of, contained within, or used as a home location by another entity.
-
C.
startVenue
Indicates the venue or location where an event, journey, or activity begins.
-
D.
isCentralVenueOf
chosen
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
-
E.
internationalVenueFor
Indicates that a location serves as a host or site for events, activities, or functions involving participants or audiences from multiple countries.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.