Triple
T33583864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leningradsky Avenue |
E860225
|
entity |
| Predicate | majorRouteTowards |
P122717
|
FINISHED |
| Object | Saint Petersburg |
—
|
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: Saint Petersburg | Statement: [Leningradsky Avenue, majorRouteTowards, Saint Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorRouteTowards Context triple: [Leningradsky Avenue, majorRouteTowards, Saint Petersburg]
-
A.
majorRouteTo
chosen
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
B.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
C.
firstMajorRoute
Indicates that the specified route is the primary or earliest major route associated with an entity (such as a location, project, or network).
-
D.
formerMainRouteBetween
Indicates that a route once served as the primary connection between two locations but no longer holds that status.
-
E.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 1, 2026, 1:40 a.m.