Triple
T33720970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neostethus |
E864010
|
entity |
| Predicate | maleReproductiveOrganLocation |
P177246
|
FINISHED |
| Object | anterior ventral region |
—
|
LITERAL 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: anterior ventral region | Statement: [Neostethus, maleReproductiveOrganLocation, anterior ventral region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maleReproductiveOrganLocation Context triple: [Neostethus, maleReproductiveOrganLocation, anterior ventral region]
-
A.
reproductiveSystem
Indicates a relationship where one entity is the reproductive system of another, responsible for producing offspring or reproductive cells.
-
B.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
C.
maleLength
Indicates that the relationship specifies the length or size measurement of a male individual or male part of an entity.
-
D.
genitalsProduced
Indicates that one entity has produced or generated the genitals of another entity.
-
E.
fromGenitals
Indicates that something originates from, is emitted by, or is derived from the genitals.
- F. None of above. chosen
Provenance (4 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6faeac9288190ac7ce78ea3cdb622 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:44 a.m.