Triple

T12933648
Position Surface form Disambiguated ID Type / Status
Subject Germano E309446 entity
Predicate hasVariant P455 FINISHED
Object Germán E309445 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: Germán | Statement: [Germano, hasVariant, Germán]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Germán
Context triple: [Germano, hasVariant, Germán]
  • A. Germán chosen
    Germán is a Spanish given name, commonly used in Spanish-speaking countries and derived from the same roots as the name Germain.
  • B. Germano
    Germano is a masculine given name and surname of Romance-language origin, cognate with the French name Germain.
  • C. Parlatino
    Parlatino is a regional parliamentary organization that brings together the legislative bodies of Latin American countries to promote political integration, democracy, and cooperation across the region.
  • D. Gallego
    Gallego is a Spanish surname commonly associated with people of Galician origin or ancestry.
  • E. Española
    Española is the former Spanish name for the Caribbean island now known as Hispaniola, which is shared by Haiti and the Dominican Republic.
  • 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_69d7bdfa933c8190b5a27aa4a08a19b7 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d97dc6517481908637781da240b51f completed April 10, 2026, 10:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6af6a830881908ab238b250d2c7d5 completed May 3, 2026, 2:14 a.m.
Created at: April 9, 2026, 5:42 p.m.