Triple

T14751872
Position Surface form Disambiguated ID Type / Status
Subject Aurelius Ambrosius E346628 entity
Predicate legendaryDeed P36130 FINISHED
Object bringing the Giant’s Dance from Ireland 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: bringing the Giant’s Dance from Ireland | Statement: [Aurelius Ambrosius, legendaryDeed, bringing the Giant’s Dance from Ireland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legendaryDeed
Context triple: [Aurelius Ambrosius, legendaryDeed, bringing the Giant’s Dance from Ireland]
  • A. notableDeed chosen
    Indicates that an entity is recognized for performing a significant or noteworthy action or achievement.
  • B. legendaryDeath
    Indicates a death that is renowned or celebrated in stories or history, often marked by extraordinary circumstances or lasting fame.
  • C. achievementDefinition
    Indicates that one entity specifies or defines the criteria, properties, or structure of an achievement associated with another entity.
  • D. mythicReputation
    Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
  • E. legendaryMotive
    Indicates a motive or driving reason behind an action or state that is regarded as legendary, iconic, or of mythic significance.
  • 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_69d822e6f1c88190bc494d491a907114 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7d40efc8190bb1be34c19a2b57c completed April 14, 2026, 11:03 p.m.
PD Predicate disambiguation batch_69de8bf9331481909582045cd567d91f completed April 14, 2026, 6:48 p.m.
Created at: April 10, 2026, 1:30 a.m.