Triple
T28740076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leishmania donovani |
E731212
|
entity |
| Predicate | locationInHost |
P187838
|
FINISHED |
| Object | macrophages |
—
|
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: macrophages | Statement: [Leishmania donovani, locationInHost, macrophages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInHost Context triple: [Leishmania donovani, locationInHost, macrophages]
-
A.
cellLocationInHost
chosen
Indicates the location or position of a cell within its host organism or host environment.
-
B.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
C.
locationRelativeToIP
Indicates a spatial or geographic relationship between an entity and a given IP address’s inferred location.
-
D.
hostingLocation
Indicates the place or venue where an event, activity, or entity is being hosted or takes place.
-
E.
coreLocation
Indicates that one entity serves as the central or primary location associated with another entity.
- 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_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: April 28, 2026, 6:02 a.m.