Triple
T12308357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kornhamnstorg |
E293409
|
entity |
| Predicate | hasStreetAddressSystem |
P49387
|
FINISHED |
| Object | Stockholm street addressing |
—
|
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: Stockholm street addressing | Statement: [Kornhamnstorg, hasStreetAddressSystem, Stockholm street addressing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetAddressSystem Context triple: [Kornhamnstorg, hasStreetAddressSystem, Stockholm street addressing]
-
A.
hasStreetNumberingSystem
chosen
Indicates that a location or area uses an organized system for assigning numbers to buildings or addresses along its streets.
-
B.
hasRoadNumberSystem
Indicates that a place or region uses a specific system for assigning numbers to its roads or highways.
-
C.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
D.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
-
E.
hasPostalAddressSystem
Indicates that an entity possesses or is served by an organized system for assigning and managing postal addresses.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.