Triple

T10025487
Position Surface form Disambiguated ID Type / Status
Subject Reitia E200712 entity
Predicate possibleInterpretatioRomana P91771 FINISHED
Object association with Roman goddesses 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: association with Roman goddesses | Statement: [Reitia, possibleInterpretatioRomana, association with Roman goddesses]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleInterpretatioRomana
Context triple: [Reitia, possibleInterpretatioRomana, association with Roman goddesses]
  • A. preRomanLanguage
    Indicates that a language existed or was used in a region before the arrival or dominance of Roman rule or the Latin language.
  • B. underRomanRule
    Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
  • C. romanNomen
    Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
  • D. intendedInterpretation
    Indicates that one entity is meant to be understood or interpreted in a particular way, sense, or meaning relative to another.
  • E. disputedInterpretation
    Indicates that there is disagreement or contention over how something should be understood, interpreted, or explained.
  • 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_69ca831c45f08190ac1505cc15076608 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cdcde2009081908eddda7813617df4 completed April 2, 2026, 2:01 a.m.
PD Predicate disambiguation batch_69cd4b7cd4208190b2253583ee2f892c completed April 1, 2026, 4:44 p.m.
PDg Predicate description generation batch_69cd4f8d9b888190b8067bd916dae773 completed April 1, 2026, 5:02 p.m.
Created at: March 30, 2026, 8:53 p.m.