Triple

T4577224
Position Surface form Disambiguated ID Type / Status
Subject Colonia Julia Firma Secundanorum Arausio E123166 entity
Predicate hasWellPreservedMonuments P42084 FINISHED
Object true 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: true | Statement: [Colonia Julia Firma Secundanorum Arausio, hasWellPreservedMonuments, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWellPreservedMonuments
Context triple: [Colonia Julia Firma Secundanorum Arausio, hasWellPreservedMonuments, true]
  • A. hasNumberOfMonuments
    Indicates the specific count of monuments associated with or present in a given entity.
  • B. hasPreservedBuildings chosen
    Indicates that an entity possesses buildings that have been maintained or kept in their original or historical condition.
  • C. hasHistoricSite
    Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
  • D. hasWorldHeritageSite
    Indicates that a location or entity possesses or contains a site designated as a UNESCO World Heritage Site.
  • E. otherMonuments
    Indicates that there exists a relationship between an entity and additional monuments that are associated with or related to it in some relevant way.
  • 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_69bd46466c7081909d07f36be2d08804 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd58e153908190ac8f578e03aecdfc completed March 20, 2026, 2:25 p.m.
PD Predicate disambiguation batch_69bd5228b70c8190ac48705e35a710c1 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:10 p.m.