Triple
T15974658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circuit Paul Ricard |
E387412
|
entity |
| Predicate | F1ReturnHost |
P120690
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Circuit Paul Ricard, F1ReturnHost, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: F1ReturnHost Context triple: [Circuit Paul Ricard, F1ReturnHost, 2018]
-
A.
regularF1HostFrom
Indicates that an entity regularly serves as the host location for Formula 1 events originating from a specified place or jurisdiction.
-
B.
networkHost
Indicates that one entity serves as the host machine or node on which another networked entity (such as a service, application, or connection) resides or operates.
-
C.
originalHost
Indicates that one entity is the initial or primary host on which another entity first resided, originated, or was hosted.
-
D.
currentHost
Indicates that one entity is the present or active host for another entity or process.
-
E.
featuresHosts
Indicates that one entity serves as the host or platform on which another entity is presented, run, or made available.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:54 a.m.