Triple
T12587268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolshoy Petrovsky Bridge |
E300497
|
entity |
| Predicate | connectsGeographicalFeatureType |
P41624
|
FINISHED |
| Object | river banks |
—
|
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: river banks | Statement: [Bolshoy Petrovsky Bridge, connectsGeographicalFeatureType, river banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsGeographicalFeatureType Context triple: [Bolshoy Petrovsky Bridge, connectsGeographicalFeatureType, river banks]
-
A.
connectsLandform
chosen
Indicates a relationship where one landform serves as a physical link or passage between two or more other landforms.
-
B.
connectsProvincesAlong
Indicates a relationship where something serves as a link or route joining multiple provinces along a specified path or alignment.
-
C.
refersToGeographicFeature
Indicates that one entity makes reference to, denotes, or is associated with a specific geographic feature such as a landform, body of water, or other physical location.
-
D.
connectsPeninsulaTo
Indicates a relationship where a geographic feature or structure links a peninsula to another landmass or area.
-
E.
connectsRegions
Indicates a relationship where one entity links or joins two or more distinct regions, enabling passage, interaction, or continuity between them.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:05 p.m.