Triple
T26461721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Austrian Grand Prix |
E665655
|
entity |
| Predicate | heldBehindClosedDoors |
P150074
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2020 Austrian Grand Prix, heldBehindClosedDoors, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldBehindClosedDoors Context triple: [2020 Austrian Grand Prix, heldBehindClosedDoors, true]
-
A.
meetsBehindClosedDoors
Indicates that one entity meets with another in a private, non-public setting where others are excluded from the interaction.
-
B.
playedBehindClosedDoors
chosen
Indicates that an event or game took place without spectators present, typically barring public attendance.
-
C.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
-
D.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
E.
hasNumberOfFalseDoors
Indicates that an entity is associated with a specific count of false doors (door-like architectural features that do not function as actual entrances or exits).
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612956424819083b0e451342a5811 |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 12:13 a.m.