Triple

T25903319
Position Surface form Disambiguated ID Type / Status
Subject Rhyticeros E652677 entity
Predicate hasSpecies P965 FINISHED
Object Rhyticeros leucocephalus
Rhyticeros leucocephalus is a species of hornbill, a large forest-dwelling bird known for its prominent bill and casque, found in parts of Southeast Asia.
E652677 NE 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: Rhyticeros leucocephalus | Statement: [Rhyticeros, hasSpecies, Rhyticeros leucocephalus]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Rhyticeros leucocephalus
Triple: [Rhyticeros, hasSpecies, Rhyticeros leucocephalus]
Generated description
Rhyticeros leucocephalus is a species of hornbill, a large forest-dwelling bird known for its prominent bill and casque, found in parts of Southeast Asia.

Provenance (5 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_69e7ab3d3f8481909bc53ed64c06af33 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f603bbcc5c8190a4c63ef469e78276 completed May 2, 2026, 2:01 p.m.
NED1 Entity disambiguation (via context triple) batch_6a118f87799c8190819ce404acd7da3e completed May 23, 2026, 11:29 a.m.
NEDg Description generation batch_6a119053e3b0819092c8e62b5b4ae02a completed May 23, 2026, 11:32 a.m.
NED2 Entity disambiguation (via description) batch_6a1190db5ab48190a5b902fee03abdde completed May 23, 2026, 11:34 a.m.
Created at: April 22, 2026, 8:26 a.m.