Triple

T25333581
Position Surface form Disambiguated ID Type / Status
Subject Bunopithecus E635216 entity
Predicate wasOnceThoughtToInclude P52471 FINISHED
Object living hoolock gibbons 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: living hoolock gibbons | Statement: [Bunopithecus, wasOnceThoughtToInclude, living hoolock gibbons]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasOnceThoughtToInclude
Context triple: [Bunopithecus, wasOnceThoughtToInclude, living hoolock gibbons]
  • A. formerlyIncluded chosen
    Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
  • B. sometimesIncluded
    Indicates that one entity is occasionally, but not always, contained within, part of, or present in association with another entity.
  • C. initiallyIncluded
    Indicates that an entity was part of a specified set, group, or configuration at the beginning of a process, period, or state.
  • D. usedToBePartOf
    Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
  • E. consideredIn
    Indicates that one entity is taken into account, examined, or included as a factor within the context, scope, or decision framework of another entity.
  • 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_69e75a99bd6481909476115b35b9a8e4 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f497c80e0881908227999fa2c4e0d6 completed May 1, 2026, 12:08 p.m.
PD Predicate disambiguation batch_69f45d0dbc8c8190beecce679fce90a4 completed May 1, 2026, 7:58 a.m.
Created at: April 21, 2026, 1:31 p.m.