Triple

T1292218
Position Surface form Disambiguated ID Type / Status
Subject Edinburgh Castle E27571 entity
Predicate earliestRecordedFortification P28167 FINISHED
Object 7th century 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: 7th century | Statement: [Edinburgh Castle, earliestRecordedFortification, 7th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: earliestRecordedFortification
Context triple: [Edinburgh Castle, earliestRecordedFortification, 7th century]
  • A. oldestStandingStructureIn
    Indicates that one entity is the oldest still-existing structure located within the specified place or region.
  • B. constructionBeganAsFortressIn
    Indicates that the construction of something originally began with the purpose or function of serving as a fortress at a specified time or in a specified place.
  • C. fortressBuiltUnder
    Indicates that one structure or location was constructed directly beneath or within the protective area of a fortress.
  • D. castleBuiltFor
    Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
  • E. historicalStronghold
    Indicates that a location has historically served as a fortified center of power, defense, or control for a group or authority.
  • 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_69a496d4ec448190ad653b2590c46711 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c0d7d15081909d3af19b9297f1cc completed March 1, 2026, 10:42 p.m.
PD Predicate disambiguation batch_69a4bee41ca08190b0ad6f7ea40c0b62 completed March 1, 2026, 10:34 p.m.
PDg Predicate description generation batch_69a4bfa205ec81909d8170b398345615 completed March 1, 2026, 10:37 p.m.
Created at: March 1, 2026, 7:51 p.m.