Triple
T15811001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chalkhill blue butterfly |
E383351
|
entity |
| Predicate | larvalFoodPlantCommonName |
P98593
|
FINISHED |
| Object | horseshoe vetch |
—
|
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: horseshoe vetch | Statement: [chalkhill blue butterfly, larvalFoodPlantCommonName, horseshoe vetch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: larvalFoodPlantCommonName Context triple: [chalkhill blue butterfly, larvalFoodPlantCommonName, horseshoe vetch]
-
A.
likelyFoodPlants
chosen
Indicates that certain plants are probable or suitable candidates to be used as food sources.
-
B.
edibleSpecies
Indicates that one species can be safely eaten as food by another species or by humans.
-
C.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
D.
isMajorFoodSourceFor
Indicates that something serves as a primary or significant source of food for another entity.
-
E.
growsOn
Indicates that one entity develops or increases in size, number, or extent while being physically supported by or attached to 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52aae14819091de08630e7e1d1a |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.