Triple
T35753180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Grand Prix |
E1033370
|
entity |
| Predicate | traditionalCircuit |
P200109
|
FINISHED |
| Object | Nürburgring |
—
|
NE NERFINISHED |
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: Nürburgring | Statement: [German Grand Prix, traditionalCircuit, Nürburgring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalCircuit Context triple: [German Grand Prix, traditionalCircuit, Nürburgring]
-
A.
typicalCircuit
Indicates that one entity is a standard or commonly occurring circuit configuration or pattern associated with another entity.
-
B.
typicalCircuitType
Indicates that one entity is the usual or standard type of circuit associated with another entity.
-
C.
circuit
Indicates that one entity forms or participates in an electrical or logical pathway that allows current or signals to flow through a connected system involving another entity.
-
D.
typeOfCircuit
Indicates that one entity is classified as a specific kind or category of electrical circuit represented by the other entity.
-
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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_69ff7594c6c081909e812e4e04e63530 |
completed | May 9, 2026, 5:57 p.m. |
Created at: May 3, 2026, 4:06 p.m.