Triple

T5428960
Position Surface form Disambiguated ID Type / Status
Subject Visby E121435 entity
Predicate cityWallLength P63706 FINISHED
Object approximately 3.4 kilometres 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: approximately 3.4 kilometres | Statement: [Visby, cityWallLength, approximately 3.4 kilometres]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cityWallLength
Context triple: [Visby, cityWallLength, approximately 3.4 kilometres]
  • A. enclosureWallHeight
    Indicates the height of the wall that forms the boundary or enclosure around an area or structure.
  • B. roadLength
    Indicates the measured distance or extent of a road, typically expressed in units of length.
  • C. hasOuterWall
    Indicates that one entity possesses or is surrounded by an external enclosing wall that defines its outer boundary.
  • D. outfieldWallHeight
    Indicates the height of the wall that defines the boundary of the outfield area in a ballpark or playing field.
  • E. lengthOfMainBuilding
    Indicates the measured physical length of the main building in the context of a larger structure or site.
  • F. None of above. chosen

Provenance (4 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_69bd463c65f0819082ee6483ab4b466a completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd8911a7348190ad9378a248190f07 completed March 20, 2026, 5:51 p.m.
PD Predicate disambiguation batch_69bd846b8bdc81909dcdc2a3084226f2 completed March 20, 2026, 5:31 p.m.
PDg Predicate description generation batch_69bd8910de688190aa0cd80627849a60 completed March 20, 2026, 5:51 p.m.
Created at: March 20, 2026, 2:06 p.m.