Triple
T21883063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch Grand Prix |
E540336
|
entity |
| Predicate | hostCircuitLengthPost2020 |
P44364
|
FINISHED |
| Object | approximately 4.259 km |
—
|
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: approximately 4.259 km | Statement: [Dutch Grand Prix, hostCircuitLengthPost2020, approximately 4.259 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCircuitLengthPost2020 Context triple: [Dutch Grand Prix, hostCircuitLengthPost2020, approximately 4.259 km]
-
A.
circuitLength
chosen
Indicates the total measured length or distance of a circuit or closed path.
-
B.
hostCircuitOpened
Indicates that the electrical circuit associated with the host has been opened, interrupting current flow or connectivity.
-
C.
hostedByCircuit
Indicates that an event, activity, or process is organized, managed, or carried out under the responsibility or auspices of a particular circuit.
-
D.
numberOfCircuits
Indicates the total count of circuits associated with or contained in a given entity or system.
-
E.
networkLength
Indicates the total measured extent or distance covered by a network (e.g., of connections, links, or paths).
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e9d3508190aadcfcdac0376387 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.