Triple

T7669274
Position Surface form Disambiguated ID Type / Status
Subject defensive complex of Saint Petersburg E173705 entity
Predicate followsDesignTradition P68934 FINISHED
Object bastion fort system 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: bastion fort system | Statement: [defensive complex of Saint Petersburg, followsDesignTradition, bastion fort system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: followsDesignTradition
Context triple: [defensive complex of Saint Petersburg, followsDesignTradition, bastion fort system]
  • A. sharesDesignTraditionWith
    Indicates that two entities originate from or participate in the same design tradition, sharing common stylistic principles, methods, or heritage.
  • B. linkedToTradition chosen
    Indicates a relationship where something is connected or related to a particular tradition, heritage, or customary practice.
  • C. traditionIncludes
    Indicates that a particular tradition encompasses, contains, or is composed of a specified element, practice, or component.
  • D. traditionInheritedFrom
    Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
  • E. followsCouncilTradition
    Indicates that an entity adheres to established customs, practices, or precedents set by a council.
  • 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_69c699562484819086752091e3164a27 completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7063dab1881909598b04999b8b690 completed March 27, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69c7015f7430819099d3ea2781b7cee2 completed March 27, 2026, 10:14 p.m.
Created at: March 27, 2026, 4 p.m.