Triple
T19280259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushkin Street |
E482167
|
entity |
| Predicate | typicalPositionInCity |
P112307
|
FINISHED |
| Object | city center |
—
|
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: city center | Statement: [Pushkin Street, typicalPositionInCity, city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPositionInCity Context triple: [Pushkin Street, typicalPositionInCity, city center]
-
A.
typicalPositionType
chosen
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
-
B.
hasRelativePositionInCity
Indicates that one entity occupies a specific spatial or positional relationship within the boundaries or layout of a particular city.
-
C.
hasCoordinateInCityCentreApprox
Indicates that an entity’s location is approximately within the central area of a city, based on its geographic coordinates.
-
D.
typicalVenueCity
Indicates that a particular city is the usual or standard location where an event, activity, or organization is typically held or based.
-
E.
typicalCityLatitude
Indicates the usual or representative latitude at which a given city is located.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbfdfaf481909e0434f33053cc62 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.