Triple

T31445418
Position Surface form Disambiguated ID Type / Status
Subject Brava Centauri E802172 entity
Predicate hasInUniversePopulationType P90440 FINISHED
Object humans 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: humans | Statement: [Brava Centauri, hasInUniversePopulationType, humans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInUniversePopulationType
Context triple: [Brava Centauri, hasInUniversePopulationType, humans]
  • A. hasInUniverseInhabitants chosen
    Indicates that a universe or fictional setting contains certain beings or populations as its inhabitants.
  • B. hasPopulationType
    Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
  • C. inUniverseType
    Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
  • D. hasGalaxyPopulation
    Indicates that a galaxy possesses or is associated with a certain number or group of inhabitants or stellar objects constituting its population.
  • E. inUniverseLocationType
    Indicates the type or category of location that something occupies within a fictional or defined universe or setting.
  • 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_69f348c5a6bc819092a557e95438976f completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69ff409ff5548190849c2d50e99bd807 completed May 9, 2026, 2:11 p.m.
PD Predicate disambiguation batch_69ff401a5e188190a72f945e910b4a6c completed May 9, 2026, 2:09 p.m.
Created at: April 30, 2026, 9:09 p.m.