Triple
T18783868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diptera |
E459324
|
entity |
| Predicate | includesPestGroup |
P133001
|
FINISHED |
| Object | fruit flies |
—
|
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: fruit flies | Statement: [Diptera, includesPestGroup, fruit flies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPestGroup Context triple: [Diptera, includesPestGroup, fruit flies]
-
A.
notablePest
Indicates that an entity is recognized as a significant or impactful pest, typically causing notable harm, damage, or nuisance.
-
B.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
C.
includesParasiticTaxa
Indicates that the referenced group or set contains taxa that live parasitically on or within other organisms.
-
D.
animalGroupIncluded
Indicates that a particular animal is a member of, or belongs to, a specified animal group.
-
E.
introducedPest
Indicates that an organism has been brought by humans into a new area where it is considered a pest.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5977f34e48190a9932af330ea4f92 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.