Triple
T28740075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leishmania donovani |
E731212
|
entity |
| Predicate | locationInVector |
P76038
|
FINISHED |
| Object | midgut of sandfly |
—
|
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: midgut of sandfly | Statement: [Leishmania donovani, locationInVector, midgut of sandfly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInVector Context triple: [Leishmania donovani, locationInVector, midgut of sandfly]
-
A.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
B.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
C.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
D.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
E.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: April 28, 2026, 6:02 a.m.