Triple
T27788795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavicalis |
E701025
|
entity |
| Predicate | associatedWithPlantType |
P156731
|
FINISHED |
| Object | flowering trees |
—
|
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: flowering trees | Statement: [Gavicalis, associatedWithPlantType, flowering trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPlantType Context triple: [Gavicalis, associatedWithPlantType, flowering trees]
-
A.
hostPlantType
chosen
Indicates the type or category of plant that serves as a host for another organism (such as an insect, fungus, or parasite).
-
B.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
C.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
-
D.
containsPlantsWith
Indicates that one entity includes or holds within it one or more plant entities.
-
E.
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).
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a006fe981488190b4287289a3327664 |
completed | May 10, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_6a006f6976ec8190ba2c04fbaa946345 |
completed | May 10, 2026, 11:43 a.m. |
Created at: April 27, 2026, 5:26 p.m.