Triple
T23013316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firestone Grand Prix of St. Petersburg |
E572962
|
entity |
| Predicate | hasPaddockLocation |
P150671
|
FINISHED |
| Object | near waterfront |
—
|
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: near waterfront | Statement: [Firestone Grand Prix of St. Petersburg, hasPaddockLocation, near waterfront]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaddockLocation Context triple: [Firestone Grand Prix of St. Petersburg, hasPaddockLocation, near waterfront]
-
A.
hasPaddock
Indicates that one entity possesses or is associated with a specific paddock area or enclosure.
-
B.
hasPaddockAccess
Indicates that one entity is permitted to enter or use a particular paddock area associated with another entity.
-
C.
hasStabling
Indicates that one entity provides or contains stabling facilities (such as stalls or accommodation) for another, typically for animals like horses.
-
D.
hasStablingCapacity
Indicates the maximum number of animals or vehicles that a facility can accommodate for stabling or storage.
-
E.
hasPorchLocation
Indicates the spatial location or placement of a porch relative to another referenced 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e300008190bb12c6388a8b3280 |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:51 p.m.