Triple

T33843995
Position Surface form Disambiguated ID Type / Status
Subject Lavelua (King of Uvea) E867427 entity
Predicate hasAlternativeFormOfName P110696 FINISHED
Object Lavelua of Uvea 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: Lavelua of Uvea | Statement: [Lavelua (King of Uvea), hasAlternativeFormOfName, Lavelua of Uvea]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternativeFormOfName
Context triple: [Lavelua (King of Uvea), hasAlternativeFormOfName, Lavelua of Uvea]
  • A. hasAlternativeFamilyName
    Indicates that an entity is associated with an additional or variant family name besides its primary family name.
  • B. hasAlternativeToponymy
    Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
  • C. hasAlternativeNamesakeRole
    Indicates that an entity serves in an additional or alternative role as a namesake, distinct from its primary namesake role.
  • D. haveAlternativeTitle chosen
    Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
  • E. hasAlternativeNameForSameRace
    Indicates that one name is an alternative designation used for the same race as another name.
  • F. None of above.

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_69f349937b648190a34ada70f6a2b534 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd64bc86848190a49f451a8fc5cf1e completed May 8, 2026, 4:21 a.m.
PD Predicate disambiguation batch_69fd5ff4a648819090756d90fd195d9a completed May 8, 2026, 4 a.m.
Created at: May 1, 2026, 1:47 a.m.