Triple

T38070261
Position Surface form Disambiguated ID Type / Status
Subject Uranian Eternals E950571 entity
Predicate distinctionFromParentRace P190242 FINISHED
Object developed unique culture on Uranus 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: developed unique culture on Uranus | Statement: [Uranian Eternals, distinctionFromParentRace, developed unique culture on Uranus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distinctionFromParentRace
Context triple: [Uranian Eternals, distinctionFromParentRace, developed unique culture on Uranus]
  • A. relatedRace
    Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
  • B. raceOfOrigin
    Indicates the racial or ethnic group from which an entity originally comes or is derived.
  • C. motherRaceOrGroup
    Indicates that an entity’s mother belongs to a specified race, ethnicity, or demographic group.
  • D. ethnicContrast
    Indicates a relationship where two or more entities are contrasted or differentiated based on their ethnic backgrounds or identities.
  • E. racialStructure
    Indicates how racial categories or groupings are organized, distributed, or structured within a given context or system.
  • 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_69f76f02a6c48190a94f3c0b3ee90cf2 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fcc42cbac48190b8d3e4c9ce140838 completed May 7, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69fcb0fc69c88190800453eb57a7e62c completed May 7, 2026, 3:34 p.m.
PDg Predicate description generation batch_69fcc42b9334819099929649b7ef68ea completed May 7, 2026, 4:56 p.m.
Created at: May 3, 2026, 4:21 p.m.