Triple
T16150671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thelohania solenopsae |
E391900
|
entity |
| Predicate | sporeLocationInHost |
P100571
|
FINISHED |
| Object | fat body of fire ants |
—
|
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: fat body of fire ants | Statement: [Thelohania solenopsae, sporeLocationInHost, fat body of fire ants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sporeLocationInHost Context triple: [Thelohania solenopsae, sporeLocationInHost, fat body of fire ants]
-
A.
sporeLocation
chosen
Indicates the location or site where spores are present, produced, or deposited in relation to another entity.
-
B.
spawningLocation
Indicates the place or environment where an entity originates, appears, or is generated.
-
C.
poolLocation
Indicates that one entity is the physical location or site where a particular pool is situated.
-
D.
sporeType
Indicates the specific kind or category of spores associated with an entity.
-
E.
deploymentLocation
Indicates the place or environment where something (such as a system, resource, or component) is deployed or put into operational use.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d9724808190a8332987583a345a |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.