Triple
T24609007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthribidae |
E609063
|
entity |
| Predicate | includesPestSpecies |
P10920
|
FINISHED |
| Object | Araecerus fasciculatus |
E1642343
|
NE 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: Araecerus fasciculatus | Statement: [Anthribidae, includesPestSpecies, Araecerus fasciculatus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPestSpecies Context triple: [Anthribidae, includesPestSpecies, Araecerus fasciculatus]
-
A.
includesPestGroup
Indicates that one entity contains or encompasses a specified group or category of pests within its scope or composition.
-
B.
includesSpecies
chosen
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
C.
notablePest
Indicates that an entity is recognized as a significant or impactful pest, typically causing notable harm, damage, or nuisance.
-
D.
introducedPest
Indicates that an organism has been brought by humans into a new area where it is considered a pest.
-
E.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
- F. None of above.
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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10047bb430819095f9b7f435485713 |
completed | May 22, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.