Triple

T31048631
Position Surface form Disambiguated ID Type / Status
Subject Bojano E791194 entity
Predicate hasAncientInfrastructure P182772 FINISHED
Object Roman roads junction 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 roads junction | Statement: [Bojano, hasAncientInfrastructure, Roman roads junction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAncientInfrastructure
Context triple: [Bojano, hasAncientInfrastructure, Roman roads junction]
  • A. usesAncientStructure
    Indicates that one entity makes use of, incorporates, or relies on an ancient structure in its function, design, or activity.
  • B. hasInfrastructureHistory
    Indicates that there exists a record or account of past changes, developments, or states of infrastructure associated with an entity.
  • C. isAncient
    Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
  • D. hasColonialInfrastructure
    Indicates that one entity possesses or is characterized by infrastructure established or developed during a period of colonial rule by another entity.
  • E. infrastructureAge
    Indicates the length of time that a piece of infrastructure has existed since its construction or installation.
  • 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_69f224ca2fa881908a3ac5fedf207b90 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f7908ec35881909a42f954fb9fa16e completed May 3, 2026, 6:14 p.m.
PD Predicate disambiguation batch_69f78e2ac3fc819081a45c6841375c8d completed May 3, 2026, 6:04 p.m.
PDg Predicate description generation batch_69f78fd3fd888190b7db0b563f298585 completed May 3, 2026, 6:11 p.m.
Created at: April 29, 2026, 9 p.m.