Triple

T9565246
Position Surface form Disambiguated ID Type / Status
Subject Amanda E230773 entity
Predicate hasRelatedName P3889 FINISHED
Object Amandus
Amandus is a masculine given name of Latin origin, historically used in various European countries and related to the name Amanda.
E807877 NE FINISHED

How this triple was built (4 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: Amandus | Statement: [Amanda, hasRelatedName, Amandus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amandus
Context triple: [Amanda, hasRelatedName, Amandus]
  • A. Armandus
    Armandus is a masculine given name, a Latinized variant of Armand, historically associated with European, particularly French and Dutch, usage.
  • B. Amelius
    Amelius was a 3rd-century Neoplatonist philosopher and disciple of Plotinus, known for his extensive commentaries on Platonic thought.
  • C. Thaddaeus
    Thaddaeus is a disciple of Jesus traditionally counted among the Twelve Apostles in Christian tradition, often identified with Jude the Apostle.
  • D. Reimund
    Reimund is a masculine given name, primarily used in German-speaking regions, that is a variant of the name Raymond.
  • E. Bertramus
    Bertramus is a Latinized variant of the given name Bertram, historically used in medieval and ecclesiastical contexts.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Amandus
Triple: [Amanda, hasRelatedName, Amandus]
Generated description
Amandus is a masculine given name of Latin origin, historically used in various European countries and related to the name Amanda.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Amandus
Target entity description: Amandus is a masculine given name of Latin origin, historically used in various European countries and related to the name Amanda.
  • A. Armandus
    Armandus is a masculine given name, a Latinized variant of Armand, historically associated with European, particularly French and Dutch, usage.
  • B. Amelius
    Amelius was a 3rd-century Neoplatonist philosopher and disciple of Plotinus, known for his extensive commentaries on Platonic thought.
  • C. Thaddaeus
    Thaddaeus is a disciple of Jesus traditionally counted among the Twelve Apostles in Christian tradition, often identified with Jude the Apostle.
  • D. Reimund
    Reimund is a masculine given name, primarily used in German-speaking regions, that is a variant of the name Raymond.
  • E. Bertramus
    Bertramus is a Latinized variant of the given name Bertram, historically used in medieval and ecclesiastical contexts.
  • F. None of above. chosen

Provenance (5 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_69ca847f22188190a56e4a97625bef22 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd996a01b081908e2782f41520f73d completed April 1, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69d152abb0788190ab2e204d9a082ccf completed April 4, 2026, 6:04 p.m.
NEDg Description generation batch_69d15565623c81908112183b65464553 completed April 4, 2026, 6:16 p.m.
NED2 Entity disambiguation (via description) batch_69d1560bbe3481908c98d74d21b33e63 completed April 4, 2026, 6:18 p.m.
Created at: March 30, 2026, 8:04 p.m.