Triple

T19312915
Position Surface form Disambiguated ID Type / Status
Subject Park an der Ilm E483015 entity
Predicate RomanHouseArchitecturalStyle P607 FINISHED
Object classical 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: classical | Statement: [Park an der Ilm, RomanHouseArchitecturalStyle, classical]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: RomanHouseArchitecturalStyle
Context triple: [Park an der Ilm, RomanHouseArchitecturalStyle, classical]
  • A. mainRomanSanctuary
    Indicates that one entity serves as the primary Roman religious sanctuary or temple associated with another entity.
  • B. architecturalStyle chosen
    Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
  • C. hasRomanRemains
    Indicates that the subject contains or is the location of physical remains or archaeological evidence from the Roman period.
  • D. RomanRepresentative
    Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
  • E. housesRemainsOf
    Indicates that one entity serves as the location or container in which the physical remains of another entity are kept or preserved.
  • 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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e604cf25c081908a30814b15d78c25 completed April 20, 2026, 10:49 a.m.
PD Predicate disambiguation batch_69e4dd0ef66881909d489d634eee817a completed April 19, 2026, 1:47 p.m.
Created at: April 10, 2026, 1:32 p.m.