Triple
T31527744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Avenue (Minsk) |
E804390
|
entity |
| Predicate | hasSiteOnStreet |
P959
|
FINISHED |
| Object | Independence Square (Minsk) |
—
|
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: Independence Square (Minsk) | Statement: [Independence Avenue (Minsk), hasSiteOnStreet, Independence Square (Minsk)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteOnStreet Context triple: [Independence Avenue (Minsk), hasSiteOnStreet, Independence Square (Minsk)]
-
A.
hasStreet
chosen
Indicates that an entity is located on, associated with, or identified by a particular street.
-
B.
hasHeadquartersOnStreet
Indicates that an organization’s headquarters is located on a specific street.
-
C.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
D.
hasStreetLevel
Indicates that something is located at, accessible from, or directly associated with the street level of a building or area.
-
E.
hasBuildingUseAlongStreet
Indicates that a building located along a particular street is used for a specified purpose or function in relation to that 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 30, 2026, 9:59 p.m.