Triple

T19419090
Position Surface form Disambiguated ID Type / Status
Subject Stone Bridge (old bridge on same site) E485797 entity
Predicate replacedInPlaceBy P29646 FINISHED
Object Bolshoy Kamenny Bridge on same site 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: Bolshoy Kamenny Bridge on same site | Statement: [Stone Bridge (old bridge on same site), replacedInPlaceBy, Bolshoy Kamenny Bridge on same site]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacedInPlaceBy
Context triple: [Stone Bridge (old bridge on same site), replacedInPlaceBy, Bolshoy Kamenny Bridge on same site]
  • A. replacedWith chosen
    Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
  • B. placedBy
    Indicates that one entity was positioned, set, or put in a location or context by another entity.
  • C. replacedBecause
    Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
  • D. replacedDuring
    Indicates that one entity took the place of another entity during a specified time period or interval.
  • E. replacedAtPar
    Indicates that one entity has been replaced by another at a specific location or position within a larger structure or sequence.
  • 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62afbaf0c8190913eda4b04efbe67 completed April 20, 2026, 1:32 p.m.
PD Predicate disambiguation batch_69e4fd68b1f881908d273de1fee81a75 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:37 p.m.