Triple

T31940400
Position Surface form Disambiguated ID Type / Status
Subject Sapajus E815507 entity
Predicate hasMember P10 FINISHED
Object Sapajus macrocephalus
Sapajus macrocephalus is a species of robust capuchin monkey native to the Amazon region, known for its large head and strong jaw adapted for cracking hard-shelled foods.
E1988975 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: Sapajus macrocephalus | Statement: [Sapajus, hasMember, Sapajus macrocephalus]
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: Sapajus macrocephalus
Triple: [Sapajus, hasMember, Sapajus macrocephalus]
Generated description
Sapajus macrocephalus is a species of robust capuchin monkey native to the Amazon region, known for its large head and strong jaw adapted for cracking hard-shelled foods.

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_69f348f3035c81908558e2339955abb3 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b2713c2881909e4d5e80aed67f09 completed May 3, 2026, 2:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2ed4d917bc8190a8ae452c8843791c completed June 14, 2026, 4:20 p.m.
NEDg Description generation batch_6a2ed5a7342c8190970ea579d519a5fe completed June 14, 2026, 4:24 p.m.
NED2 Entity disambiguation (via description) batch_6a2ed76555008190a14a24135babd7d9 completed June 14, 2026, 4:31 p.m.
Created at: May 1, 2026, 12:05 a.m.