Triple
T31978955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Bruno elfin butterfly |
E816523
|
entity |
| Predicate | hostPlantCommonName |
P123194
|
FINISHED |
| Object | broadleaf stonecrop |
—
|
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: broadleaf stonecrop | Statement: [San Bruno elfin butterfly, hostPlantCommonName, broadleaf stonecrop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostPlantCommonName Context triple: [San Bruno elfin butterfly, hostPlantCommonName, broadleaf stonecrop]
-
A.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
-
B.
hostPlantType
Indicates the type or category of plant that serves as a host for another organism (such as an insect, fungus, or parasite).
-
C.
plantName
chosen
Indicates that the associated value is the name or designated label of a plant.
-
D.
hostPlantFamily
Indicates the taxonomic plant family that serves as the host for a given organism, typically providing it with food, shelter, or a site for development.
-
E.
hostedPlantOf
Indicates that one entity serves as the host environment or substrate on which a particular plant lives, grows, or is supported.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b348d01c8190afa1fe9ece4de11a |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:11 a.m.