Triple

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

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_6a3492859fcc819099b5a3084d809992 completed June 19, 2026, 12:51 a.m.
NEDg Description generation batch_6a3492f623908190b8c2de8b46b51b10 completed June 19, 2026, 12:53 a.m.
NED2 Entity disambiguation (via description) batch_6a34936278088190a18f59f308702af2 completed June 19, 2026, 12:54 a.m.
Created at: May 1, 2026, 12:49 a.m.