Triple

T11819750
Position Surface form Disambiguated ID Type / Status
Subject Prince Luís of Orléans-Braganza E281093 entity
Predicate givenName P17 FINISHED
Object Luís E100712 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: Luís | Statement: [Prince Luís of Orléans-Braganza, givenName, Luís]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Luís
Context triple: [Prince Luís of Orléans-Braganza, givenName, Luís]
  • A. Luís chosen
    Luís is a common Portuguese male given name, historically associated with notable figures such as the poet Luís de Camões.
  • B. Fernando
    "Fernando" is a popular 1976 ballad by Swedish pop group ABBA, known for its nostalgic, storytelling lyrics and melodic harmonies.
  • C. Fernando
    Fernando is a masculine given name of Spanish and Portuguese origin, commonly used in many Spanish-speaking and Lusophone countries.
  • D. Fernando
    Fernando is the given name of Salgueiro Maia, a key Portuguese military officer who played a leading role in the Carnation Revolution.
  • E. Fernando
    Fernando was the given name of the Duke of Alba who served as governor-general, a prominent Spanish noble and military leader.
  • 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_69d6ab26aae88190b2489efcb2a24234 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5e87e488190905bc3bb6d721e56 completed April 10, 2026, 7:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69f131e1891081909cfbd9e2eb168808 completed April 28, 2026, 10:17 p.m.
Created at: April 8, 2026, 9:42 p.m.