Triple
T36372264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turgenevskaya |
E895792
|
entity |
| Predicate | hasConnectionUnderpass |
P24311
|
FINISHED |
| Object | to Chistye Prudy |
—
|
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: to Chistye Prudy | Statement: [Turgenevskaya, hasConnectionUnderpass, to Chistye Prudy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionUnderpass Context triple: [Turgenevskaya, hasConnectionUnderpass, to Chistye Prudy]
-
A.
hasUnderpass
chosen
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
-
B.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
-
C.
hasSubwayOrUnderpass
Indicates that there exists a subway or underpass connecting or located at the related entities.
-
D.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
E.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.