Triple
T8974011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liteyny Prospekt |
E214337
|
entity |
| Predicate | hasSideElement |
P69484
|
FINISHED |
| Object | sidewalks |
—
|
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: sidewalks | Statement: [Liteyny Prospekt, hasSideElement, sidewalks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideElement Context triple: [Liteyny Prospekt, hasSideElement, sidewalks]
-
A.
hasBside
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
-
B.
hasSideEvent
Indicates that an event is associated with an additional, related side event occurring alongside it.
-
C.
hasSideChain
Indicates that one entity possesses a secondary chain or branching group attached to its main structure.
-
D.
hasRecessedSide
Indicates that one entity possesses a side or surface that is set back, indented, or recessed relative to its surrounding areas.
-
E.
hasBorderElement
chosen
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6783abe48190840e652fc2acf28f |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:02 p.m.