Triple
T17286372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norisring street circuit |
E419664
|
entity |
| Predicate | cityStreetsUsed |
P121309
|
FINISHED |
| Object | Bayernstraße |
—
|
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: Bayernstraße | Statement: [Norisring street circuit, cityStreetsUsed, Bayernstraße]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityStreetsUsed Context triple: [Norisring street circuit, cityStreetsUsed, Bayernstraße]
-
A.
cityStreetUsed
chosen
Indicates that a particular city street is utilized or traversed in the course of some activity, route, or event.
-
B.
hasNumberOfStreets
Indicates the relationship that specifies how many streets are associated with or contained within a given entity.
-
C.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
D.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
E.
streetNetwork
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4378024988190aac6aec006f8f7a1 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.