Triple
T28697761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pawia Street |
E729460
|
entity |
| Predicate | nearbyStreetOrArea |
P61270
|
FINISHED |
| Object | Dzielna Street |
—
|
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: Dzielna Street | Statement: [Pawia Street, nearbyStreetOrArea, Dzielna Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyStreetOrArea Context triple: [Pawia Street, nearbyStreetOrArea, Dzielna Street]
-
A.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
B.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
-
D.
streetOrArea
Indicates that one entity is a street or area associated with, located at, or relevant to the other entity.
-
E.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 5:40 a.m.