Triple

T32776891
Position Surface form Disambiguated ID Type / Status
Subject Aversa E838231 entity
Predicate historicInfluence P12632 FINISHED
Object Norman rule 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: Norman rule | Statement: [Aversa, historicInfluence, Norman rule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicInfluence
Context triple: [Aversa, historicInfluence, Norman rule]
  • A. historicalImpact
    Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
  • B. heritageInfluence
    Indicates how one entity’s cultural, historical, or ancestral background affects or shapes another entity’s characteristics, behavior, or development.
  • C. hasHistoricalImplicationsFor
    Indicates that something influences, shapes, or significantly affects the course, interpretation, or understanding of history for something else.
  • D. hasHistoricalInfluenceFrom chosen
    Indicates that one entity’s characteristics, development, or significance have been shaped or affected by the past actions, ideas, or legacy of another entity.
  • E. facedHistoricalImpact
    Indicates that an entity has experienced or been subjected to a significant influence, consequence, or change resulting from historical events or processes.
  • 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_69f3493a824c8190938489ba69041d08 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69ffb69812808190a751853b30183e65 completed May 9, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69ffb63bdda88190a9dd8426dc0bad43 completed May 9, 2026, 10:33 p.m.
Created at: May 1, 2026, 1:13 a.m.