Triple

T23023863
Position Surface form Disambiguated ID Type / Status
Subject Archenbaut Defayis E573244 entity
Predicate hasGivenNameComponent P17 FINISHED
Object Archenbaut NE NERFINISHED

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: Archenbaut | Statement: [Archenbaut Defayis, hasGivenNameComponent, Archenbaut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Archenbaut
Context triple: [Archenbaut Defayis, hasGivenNameComponent, Archenbaut]
  • A. Archenbaut Defayis chosen
    Archenbaut Defayis is a family surname associated with individuals such as Caroline Archenbaut Defayis.
  • B. Ardelve
    Ardelve is a small village in the Lochalsh area of the Scottish Highlands, known for its scenic coastal setting near Eilean Donan Castle.
  • C. Chaintré
    Chaintré is a small wine-producing commune in eastern France’s Burgundy region, known for its vineyards and proximity to other notable Mâconnais villages.
  • D. Monkhams
    Monkhams is a suburban residential area in northeast London, known for its leafy streets and affluent character within the London Borough of Redbridge.
  • E. Amalur
    Amalur is a high-fantasy game universe known primarily as the setting for the action role-playing game "Kingdoms of Amalur: Reckoning."
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245b821008190b0e09cb02092aae1 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1847b86688190b678d0d09ecd3c3d completed April 29, 2026, 4:09 a.m.
Created at: April 17, 2026, 3:52 p.m.