Triple
T32863425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hipódromo da Gávea |
E840579
|
entity |
| Predicate | hasTurfTrack |
P166626
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hipódromo da Gávea, hasTurfTrack, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTurfTrack Context triple: [Hipódromo da Gávea, hasTurfTrack, yes]
-
A.
hasTurf
Indicates that one entity possesses, controls, or is responsible for a specific area, territory, or domain.
-
B.
hasIndoorTrack
Indicates that a place or facility includes an indoor track as one of its features or amenities.
-
C.
hasOuterTurfCourse
chosen
Indicates that a location or facility includes an outer turf (grass) course as part of its layout or structure.
-
D.
hasStreetRunningTracks
Indicates that a location or area includes street-level tracks used for running or jogging.
-
E.
hasInnerTurfCourse
Indicates that something (typically a race track or stadium) possesses an inner turf course located within its main track or field.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ceb8306c8190afe006e5522f63be |
completed | May 3, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_69f6cc177b288190904f3f23cb856d8b |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:17 a.m.