Triple
T4431766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enstone |
E95346
|
entity |
| Predicate | hasMotorRacingFacility |
P13462
|
FINISHED |
| Object | Enstone-based Formula One facility |
—
|
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: Enstone-based Formula One facility | Statement: [Enstone, hasMotorRacingFacility, Enstone-based Formula One facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotorRacingFacility Context triple: [Enstone, hasMotorRacingFacility, Enstone-based Formula One facility]
-
A.
hasMotorRacingCircuit
chosen
Indicates that a location or entity possesses, contains, or is the site of a motor racing circuit.
-
B.
hasMotorsportInvolvement
Indicates that an entity is involved in motorsport, such as through participation, organization, sponsorship, or other direct association with motor racing activities.
-
C.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
D.
hasSportsVenueType
Indicates that a sports venue is classified as being of a specific type or category (e.g., stadium, arena, court).
-
E.
hasThrillRides
Indicates that an entity offers or includes thrill rides as part of its features or attractions.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3556b71448190a3fab938853f8b87 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.