Triple

T5291431
Position Surface form Disambiguated ID Type / Status
Subject Norwegian throne E119749 entity
Predicate genderNeutralSuccession P63343 FINISHED
Object true LITERAL 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: true | Statement: [Norwegian throne, genderNeutralSuccession, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: genderNeutralSuccession
Context triple: [Norwegian throne, genderNeutralSuccession, true]
  • A. hasGenderNeutrality
    Indicates that something (such as a term, form, or expression) is neutral with respect to gender and does not specify or imply any particular gender.
  • B. namedForGender
    Indicates that one entity is named in a way that reflects or is derived from a particular gender or gender-related characteristic of another entity.
  • C. dynasticInheritance
    Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
  • D. genderNeutralNameAdopted
    Indicates that an entity has adopted or been given a name that is not specifically associated with any particular gender.
  • E. genderNeutralForm
    Indicates that one entity is a gender-neutral linguistic form or expression corresponding to another, more gendered form.
  • F. None of above. chosen

Provenance (4 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_69bd446de5648190b313a90bd96730d2 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd8682d18c8190bbb35cc75c8a7c12 completed March 20, 2026, 5:40 p.m.
PD Predicate disambiguation batch_69bd844dfdac819086efedd1cbebff84 completed March 20, 2026, 5:30 p.m.
PDg Predicate description generation batch_69bd86800630819096dad2eb2248c372 completed March 20, 2026, 5:40 p.m.
Created at: March 20, 2026, 1:52 p.m.