Triple
T29712156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norra esplanaden |
E751810
|
entity |
| Predicate | parallelStreet |
P30057
|
FINISHED |
| Object | Södra esplanaden |
—
|
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: Södra esplanaden | Statement: [Norra esplanaden, parallelStreet, Södra esplanaden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallelStreet Context triple: [Norra esplanaden, parallelStreet, Södra esplanaden]
-
A.
hasParallelStreet
chosen
Indicates that one street runs parallel to another street, maintaining a constant distance without intersecting.
-
B.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
C.
inspiredByRealStreet
Indicates that something is based on, modeled after, or creatively derived from an actual, existing street in the real world.
-
D.
crossesStreet
Indicates that an entity moves from one side of a street to the other, traversing the street’s width.
-
E.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 7:31 p.m.