Triple

T1553883
Position Surface form Disambiguated ID Type / Status
Subject Three Estates of Scotland E33155 entity
Predicate urbanComponent P30278 FINISHED
Object royal burghs 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: royal burghs | Statement: [Three Estates of Scotland, urbanComponent, royal burghs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: urbanComponent
Context triple: [Three Estates of Scotland, urbanComponent, royal burghs]
  • A. urbanDevelopment
    Indicates the process or activities through which urban areas are planned, expanded, or transformed, including changes to infrastructure, land use, and the built environment.
  • B. urbanSuccessor
    Indicates that one urban area directly follows or replaces another in a temporal or developmental sequence, serving as its successor in an urban context.
  • C. withinUrbanArea
    Indicates that one entity is located inside the spatial boundaries of an urban area associated with another entity.
  • D. neighborhood
    Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
  • E. city2
    Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
  • 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_69a885ee6db8819099502bc5ce8af881 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9407d9d1481909597af97b16512cc completed March 5, 2026, 8:36 a.m.
PD Predicate disambiguation batch_69a907b688d081908171f89010c53973 completed March 5, 2026, 4:33 a.m.
PDg Predicate description generation batch_69a9407aa20881909e747f247ccec642 completed March 5, 2026, 8:36 a.m.
Created at: March 4, 2026, 7:27 p.m.