Triple
T37990765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridge Racers |
E947816
|
entity |
| Predicate | trackSetting |
P149934
|
FINISHED |
| Object | urban circuits |
—
|
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: urban circuits | Statement: [Ridge Racers, trackSetting, urban circuits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackSetting Context triple: [Ridge Racers, trackSetting, urban circuits]
-
A.
racecourseSetting
chosen
Indicates that an event, scene, or activity takes place in the context or environment of a racecourse.
-
B.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
C.
trackSegment
Indicates a specific portion or section of a larger track or route that is treated as a distinct segment.
-
D.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
E.
trackFeature
Indicates that one entity monitors, records, or follows the behavior, state, or evolution of a particular feature associated with another entity.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:20 p.m.