Triple

T4336389
Position Surface form Disambiguated ID Type / Status
Subject Monoplacophora E97472 entity
Predicate ancestralStatus P55649 FINISHED
Object considered primitive within Mollusca 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: considered primitive within Mollusca | Statement: [Monoplacophora, ancestralStatus, considered primitive within Mollusca]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ancestralStatus
Context triple: [Monoplacophora, ancestralStatus, considered primitive within Mollusca]
  • A. ancestralGroup
    Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
  • B. hasAncestralRoots
    Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
  • C. genealogicalStatus
    Indicates the familial or ancestral relationship that one individual has to another within a genealogy.
  • D. inheritanceStatus
    Indicates the type or condition of inheritance rights or succession status that applies between related parties.
  • E. ancestor
    Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
  • 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_69b3454662a481908fbcd0bbfaa3a0a4 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3516af43081908393fd0dad3d9382 completed March 12, 2026, 11:51 p.m.
PD Predicate disambiguation batch_69b34f4e13fc8190a42c519f37959d27 completed March 12, 2026, 11:42 p.m.
PDg Predicate description generation batch_69b34ff654308190b9717526120d80d3 completed March 12, 2026, 11:44 p.m.
Created at: March 12, 2026, 11:14 p.m.