Triple

T32358264
Position Surface form Disambiguated ID Type / Status
Subject Engyprosopon E826790 entity
Predicate containsTaxon P9413 FINISHED
Object Engyprosopon maldivensis
Engyprosopon maldivensis is a species of small lefteye flounder in the genus Engyprosopon, known from marine waters around the Maldives.
E2004338 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: Engyprosopon maldivensis | Statement: [Engyprosopon, containsTaxon, Engyprosopon maldivensis]
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: Engyprosopon maldivensis
Triple: [Engyprosopon, containsTaxon, Engyprosopon maldivensis]
Generated description
Engyprosopon maldivensis is a species of small lefteye flounder in the genus Engyprosopon, known from marine waters around the Maldives.

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_69f34915a2588190bb3178f5ec2f48f4 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6be90f8e08190a3415ac7cb60dc25 completed May 3, 2026, 3:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a33e8a77ef88190bd55d81883198532 completed June 18, 2026, 12:46 p.m.
NEDg Description generation batch_6a33e9a331f481909e9f4352d2d52db6 completed June 18, 2026, 12:50 p.m.
NED2 Entity disambiguation (via description) batch_6a3440b2dae081909c86cb74dd48ff1c completed June 18, 2026, 7:02 p.m.
Created at: May 1, 2026, 12:49 a.m.