Triple

T18467270
Position Surface form Disambiguated ID Type / Status
Subject Roman city walls of Aosta E451196 entity
Predicate hasCityPlanType P123576 FINISHED
Object Roman castrum layout 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: Roman castrum layout | Statement: [Roman city walls of Aosta, hasCityPlanType, Roman castrum layout]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCityPlanType
Context triple: [Roman city walls of Aosta, hasCityPlanType, Roman castrum layout]
  • A. isPlannedCity
    Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
  • B. hasArchitecturalPlanType chosen
    Indicates that an entity has or is associated with a specific type or category of architectural plan.
  • C. cityOfPlanning
    Indicates the city where the planning or design activities for something (e.g., a project, event, or development) are carried out.
  • D. hasPlannedUrbanCharacter
    Indicates that an area exhibits an intentionally designed and organized urban form, layout, and land use pattern rather than informal or unplanned development.
  • E. partOfUrbanPlanBy
    Indicates that something is included as a component or element within an urban plan created or overseen by a specified agent.
  • 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_69d8d38465a0819099b9b42d2a662ac1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e52a8459f88190a54cae4c8cb05119 completed April 19, 2026, 7:18 p.m.
PD Predicate disambiguation batch_69e469d05cf4819099baf1665a9cf18a completed April 19, 2026, 5:36 a.m.
Created at: April 10, 2026, 11:34 a.m.