Triple
T25341022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senna–Prost collision 1990 practice crash |
E635411
|
entity |
| Predicate | hasCircuitType |
P17211
|
FINISHED |
| Object | temporary street 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: temporary street circuit | Statement: [Senna–Prost collision 1990 practice crash, hasCircuitType, temporary street circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCircuitType Context triple: [Senna–Prost collision 1990 practice crash, hasCircuitType, temporary street circuit]
-
A.
hasCircuit
Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
-
B.
usesCircuitType
Indicates that one entity employs or is implemented using a specific type of circuit.
-
C.
includesCircuitType
Indicates that one entity contains or makes use of a specified type or category of circuit.
-
D.
circuitType
chosen
Indicates the specific kind or category of electrical circuit associated with an entity.
-
E.
isCircuitFor
Indicates that one entity functions as a circuit designed, used, or intended for another entity.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:32 p.m.