Triple

T10240550
Position Surface form Disambiguated ID Type / Status
Subject Arturo E243576 entity
Predicate hasVariant P455 FINISHED
Object Artur E325012 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: Artur | Statement: [Arturo, hasVariant, Artur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Artur
Context triple: [Arturo, hasVariant, Artur]
  • A. Artur chosen
    Artur is a masculine given name of Celtic origin, commonly used in various European countries and often associated with the legendary King Arthur.
  • B. Guiderius
    Guiderius is a noble prince and one of the central heroic figures in William Shakespeare’s play "Cymbeline," known for his bravery and hidden royal identity.
  • C. Ingenried
    Ingenried is a small rural municipality in the Weilheim-Schongau district of Bavaria in southern Germany.
  • D. Ludwik
    Ludwik is a given name, primarily used in Polish, that corresponds to the name Ludwig in other European languages.
  • E. Walternate
    Walternate is the alternate-universe version of Walter Bishop and the powerful, morally complex Secretary of Defense in the TV series "Fringe."
  • 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_69d381b0f97c819085c9b45799a5fb7c completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d21e27f08190b956d351a75c7c52 completed April 7, 2026, 9:45 a.m.
NED1 Entity disambiguation (via context triple) batch_69d6f780c7808190993e7c37cb4d18a3 completed April 9, 2026, 12:49 a.m.
Created at: April 6, 2026, 11:24 a.m.