Triple
T29223541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cars on the Road (score) |
E740867
|
entity |
| Predicate | hasSettingOfSource |
P3538
|
FINISHED |
| Object | Radiator Springs |
—
|
NE NERFINISHED |
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: Radiator Springs | Statement: [Cars on the Road (score), hasSettingOfSource, Radiator Springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettingOfSource Context triple: [Cars on the Road (score), hasSettingOfSource, Radiator Springs]
-
A.
hasSetting
chosen
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
B.
hasSettingBy
Indicates that something (such as a work, event, or scenario) has its contextual environment, location, or background defined or established by a particular agent or source.
-
C.
hasSettingOfOrigin
Indicates that something originates from, or was initially set in, a particular setting or environment.
-
D.
hasSettingSymbol
Indicates that one entity uses or is associated with another entity as a symbolic representation of its setting or environment.
-
E.
hasSettingRole
Indicates that an entity participates in a setting by fulfilling a specific contextual or functional role within it.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 28, 2026, 12:16 p.m.