Triple
T4306653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancylostoma duodenale |
E99969
|
entity |
| Predicate | adultMorphology |
P21283
|
FINISHED |
| Object | curved anterior end |
—
|
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: curved anterior end | Statement: [Ancylostoma duodenale, adultMorphology, curved anterior end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adultMorphology Context triple: [Ancylostoma duodenale, adultMorphology, curved anterior end]
-
A.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
B.
anatomicalFeature
Indicates that one entity is an anatomical part, structure, or feature of another entity.
-
C.
musculature
Indicates the relationship between an entity and the structure, development, or characteristics of its muscles.
-
D.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
E.
hasBodyRegion
chosen
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
- F. None of above.
Provenance (3 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350bb78cc8190a850aca47d8711cf |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b347ff45cc8190b0cc335a94cc3d73 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:09 p.m.