Triple
T15168231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpukhovskaya |
E362414
|
entity |
| Predicate | hasConnectionToSurfaceTransport |
P69365
|
FINISHED |
| Object | bus routes nearby |
—
|
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: bus routes nearby | Statement: [Serpukhovskaya, hasConnectionToSurfaceTransport, bus routes nearby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionToSurfaceTransport Context triple: [Serpukhovskaya, hasConnectionToSurfaceTransport, bus routes nearby]
-
A.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
-
B.
hasSurfaceConnections
Indicates that one entity is linked to another through connections or interfaces that occur at or across their surfaces.
-
C.
hasTransitAccessTo
chosen
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasTransportationElement
Indicates that one entity includes, involves, or is associated with a specific transportation-related component or feature.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064dba588190a4341775b472a6d3 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.