Triple
T35753351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian Grand Prix |
E1033373
|
entity |
| Predicate | hasOvertakingOpportunities |
P42383
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Belgian Grand Prix, hasOvertakingOpportunities, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOvertakingOpportunities Context triple: [Belgian Grand Prix, hasOvertakingOpportunities, high]
-
A.
overtakingOpportunities
chosen
Indicates situations or conditions in which one entity can pass or move ahead of another within a shared path, route, or process.
-
B.
hasRightOfWay
Indicates that one entity is entitled to proceed or act before another in a shared space or interaction, without having to yield.
-
C.
canRunOver
Indicates that one entity has the ability or potential to move across or pass over another entity, typically in a way that could cause impact or damage.
-
D.
hasFreeRoads
Indicates that an entity provides or is associated with roads that can be used without paying tolls or fees.
-
E.
safetyCarPossible
Indicates that conditions are such that deploying a safety car is a valid or allowable option.
- 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_69f7a198e24881909cc292e420269a8c |
completed | May 3, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.