Triple
T27391403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golovin Avenue |
E691541
|
entity |
| Predicate | centralStreetOf |
P86862
|
FINISHED |
| Object | Tbilisi |
—
|
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: Tbilisi | Statement: [Golovin Avenue, centralStreetOf, Tbilisi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralStreetOf Context triple: [Golovin Avenue, centralStreetOf, Tbilisi]
-
A.
hasCentralStreet
chosen
Indicates that a place or area possesses a primary or main street that serves as its central thoroughfare.
-
B.
isCentralPoliticalThoroughfareOf
Indicates that a road or street serves as the main political route or corridor within a specified area, typically hosting key government or political institutions and activities.
-
C.
isMajorCommercialStreetOf
Indicates that a street serves as a primary, heavily used route for commercial activity within a specified area or locality.
-
D.
betweenStreets
Indicates that one location is situated between two specified streets, typically along a road segment bounded by those streets.
-
E.
isSuburbanStreetOf
Indicates that one entity is a street located within or characteristic of the suburban area associated with another entity.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 12:26 p.m.