Triple
T12769280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yas Marina Circuit |
E305202
|
entity |
| Predicate | hasKartingTrack |
P106808
|
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: [Yas Marina Circuit, hasKartingTrack, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKartingTrack Context triple: [Yas Marina Circuit, hasKartingTrack, yes]
-
A.
hasMotorRacingCircuit
Indicates that a location or entity possesses, contains, or is the site of a motor racing circuit.
-
B.
hasNearbyRacetrack
Indicates that one entity is located close to or in the vicinity of a racetrack.
-
C.
hasIndoorTrack
Indicates that a place or facility includes an indoor track as one of its features or amenities.
-
D.
hasPitLane
Indicates that a racing circuit, track, or similar facility includes a designated pit lane area for vehicle servicing and related activities.
-
E.
hasRacecourseFeature
Indicates that something possesses or includes a specific feature or characteristic related to a racecourse.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df3b2f88190b37b696400178795 |
completed | April 10, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:28 p.m.