Triple

T35723398
Position Surface form Disambiguated ID Type / Status
Subject Cyclemys E1032542 entity
Predicate hasSpecies P965 FINISHED
Object Cyclemys enigmatica
Cyclemys enigmatica is a species of Asian leaf turtle in the genus Cyclemys, known for its semi-aquatic habits and distinctive, often cryptic shell patterning.
E1032542 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: Cyclemys enigmatica | Statement: [Cyclemys, hasSpecies, Cyclemys enigmatica]
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: Cyclemys enigmatica
Triple: [Cyclemys, hasSpecies, Cyclemys enigmatica]
Generated description
Cyclemys enigmatica is a species of Asian leaf turtle in the genus Cyclemys, known for its semi-aquatic habits and distinctive, often cryptic shell patterning.

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_69f76e102b5881909e5d63a30a5cecbe completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a12f87c48190a0b36604f3c7d0ae completed May 3, 2026, 7:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38a4d4365c8190a95590a9dfce92fd completed June 22, 2026, 2:58 a.m.
NEDg Description generation batch_6a38a57d5e2c81908a749015ac6fcd7f completed June 22, 2026, 3:01 a.m.
NED2 Entity disambiguation (via description) batch_6a38a5fa291c81909955855947ef19d5 completed June 22, 2026, 3:03 a.m.
Created at: May 3, 2026, 4:05 p.m.