Triple

T14192155
Position Surface form Disambiguated ID Type / Status
Subject Armand E351737 entity
Predicate hasVariant P455 FINISHED
Object Armandus E219481 NE 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: Armandus | Statement: [Armand, hasVariant, Armandus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Armandus
Context triple: [Armand, hasVariant, Armandus]
  • A. Armandus chosen
    Armandus is a masculine given name, a Latinized variant of Armand, historically associated with European, particularly French and Dutch, usage.
  • B. Amandus
    Amandus is a masculine given name of Latin origin, historically used in various European countries and related to the name Amanda.
  • C. Amelius
    Amelius was a 3rd-century Neoplatonist philosopher and disciple of Plotinus, known for his extensive commentaries on Platonic thought.
  • D. Thaddaeus
    Thaddaeus is a disciple of Jesus traditionally counted among the Twelve Apostles in Christian tradition, often identified with Jude the Apostle.
  • E. Raimundus
    Raimundus is a Latinized given name historically used across medieval Europe, often associated with various saints, scholars, and nobles.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d827894ac0819097803e57f3227b23 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61e0a52081908213aa6e548d4418 completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd194951d481909a8e81f2d09feefa completed May 7, 2026, 10:59 p.m.
Created at: April 10, 2026, 1:04 a.m.