Triple

T27505783
Position Surface form Disambiguated ID Type / Status
Subject Donacobiidae E694273 entity
Predicate recognizedAsDistinctFamily P63805 FINISHED
Object 20th century 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: 20th century | Statement: [Donacobiidae, recognizedAsDistinctFamily, 20th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recognizedAsDistinctFamily
Context triple: [Donacobiidae, recognizedAsDistinctFamily, 20th century]
  • A. recognizedAsSeparateFamily chosen
    Indicates that one entity is formally acknowledged or classified as belonging to a distinct, separate family from another entity.
  • B. identifiedAsFamilyIn
    Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
  • C. treatsAsFamily
    Indicates that one entity regards and behaves toward another with the closeness, care, and obligations typically reserved for family members.
  • D. representsFamily
    Indicates that one entity is related to another through a familial relationship (by blood, marriage, or adoption).
  • E. hasRepresentativeFamily
    Indicates that an entity is associated with a particular family that serves as its representative or characteristic example.
  • 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_69ef538370888190b1ddf53bb4831188 completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f6b903538481909cffcb6cc1cc0e70 completed May 3, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69f6b626120c819097c9ad04487570d7 completed May 3, 2026, 2:42 a.m.
Created at: April 27, 2026, 1:13 p.m.