Triple
T27056864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogilyovskaya Street |
E684920
|
entity |
| Predicate | hasRelatedStructure |
P127699
|
FINISHED |
| Object | Mogilyovsky Bridge |
—
|
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: Mogilyovsky Bridge | Statement: [Mogilyovskaya Street, hasRelatedStructure, Mogilyovsky Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedStructure Context triple: [Mogilyovskaya Street, hasRelatedStructure, Mogilyovsky Bridge]
-
A.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
B.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
C.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
-
D.
relatedToStructureType
chosen
Indicates that one entity has an association or connection with a particular type or category of structure.
-
E.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 27, 2026, 8:18 a.m.