Triple
T4384479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bahrain Grand Prix |
E99207
|
entity |
| Predicate | usedLayoutForF1 |
P10827
|
FINISHED |
| Object | Grand Prix Circuit |
—
|
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: Grand Prix Circuit | Statement: [Bahrain Grand Prix, usedLayoutForF1, Grand Prix Circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLayoutForF1 Context triple: [Bahrain Grand Prix, usedLayoutForF1, Grand Prix Circuit]
-
A.
hasLayout
chosen
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
B.
usedOnFront
Indicates that something is applied, displayed, or positioned on the front side or front-facing part of another object or entity.
-
C.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
D.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
-
E.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.