Triple
T3068692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Dhabi Grand Prix |
E62166
|
entity |
| Predicate | lightingSystem |
P1280
|
FINISHED |
| Object | full-circuit floodlighting |
—
|
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: full-circuit floodlighting | Statement: [Abu Dhabi Grand Prix, lightingSystem, full-circuit floodlighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightingSystem Context triple: [Abu Dhabi Grand Prix, lightingSystem, full-circuit floodlighting]
-
A.
hasLighting
chosen
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
B.
lightingDesigner
Indicates that an entity is responsible for planning, creating, or supervising the lighting design for a production, event, or environment.
-
C.
lightingColor
Indicates the color or hue of the lighting applied to or associated with an entity.
-
D.
usesLightingFor
Indicates that one entity employs or relies on a particular lighting setup, technology, or condition to achieve a purpose or perform an action.
-
E.
lightingOrder
Indicates the sequence or priority in which lighting elements are activated, adjusted, or controlled relative to one another.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0ffcc208190962cc9edcbf43c31 |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.