Triple
T26390360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spielberg |
E663393
|
entity |
| Predicate | hasCircuitLayoutType |
P167286
|
FINISHED |
| Object | permanent road course |
—
|
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: permanent road course | Statement: [Spielberg, hasCircuitLayoutType, permanent road course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCircuitLayoutType Context triple: [Spielberg, hasCircuitLayoutType, permanent road course]
-
A.
hasCircuitLayout
Indicates that one entity possesses, includes, or is associated with a specific circuit layout design of another entity.
-
B.
hasCircuit
Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
-
C.
usesCircuitType
Indicates that one entity employs or is implemented using a specific type of circuit.
-
D.
includesCircuitType
Indicates that one entity contains or makes use of a specified type or category of circuit.
-
E.
circuitType
Indicates the specific kind or category of electrical circuit associated with an entity.
- F. None of above. chosen
Provenance (4 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 26, 2026, 11:25 p.m.