Triple
T11893651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autódromo José Carlos Pace |
E282980
|
entity |
| Predicate | regularF1HostFrom |
P102109
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Autódromo José Carlos Pace, regularF1HostFrom, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularF1HostFrom Context triple: [Autódromo José Carlos Pace, regularF1HostFrom, 1990]
-
A.
hostedFirst
Indicates that one entity acted as the initial host for another entity, preceding any subsequent hosts.
-
B.
originalHost
Indicates that one entity is the initial or primary host on which another entity first resided, originated, or was hosted.
-
C.
firstStageHost
Indicates that an entity serves as the initial host in a multi-stage process or lifecycle involving another entity.
-
D.
hostFranchise
Indicates that one entity serves as the host organization or location for a particular franchise associated with another entity.
-
E.
guestHosted
Indicates that one entity temporarily hosted or presented an event, show, or program in place of or alongside the usual host.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1172988190a2c13d37220f2f93 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.