Triple
T35752542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 German Grand Prix |
E1033353
|
entity |
| Predicate | hostedOnLayout |
P130329
|
FINISHED |
| Object | Hockenheimring Grand Prix Circuit |
—
|
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: Hockenheimring Grand Prix Circuit | Statement: [2016 German Grand Prix, hostedOnLayout, Hockenheimring Grand Prix Circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedOnLayout Context triple: [2016 German Grand Prix, hostedOnLayout, Hockenheimring Grand Prix Circuit]
-
A.
hostedWithin
Indicates that one entity is contained, organized, or held inside the scope, space, or context of another entity.
-
B.
basedOnLayout
chosen
Indicates that one entity is derived from, structured according to, or determined by the layout or spatial arrangement defined by another entity.
-
C.
onLayout
Indicates that a layout-related event or process is occurring or has occurred for a given entity, typically involving the arrangement or positioning of its components.
-
D.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
E.
hostedAfter
Indicates that one hosting event occurred later in time than another hosting event.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.