Triple
T1358014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ampelocera |
E29032
|
entity |
| Predicate | isVascularPlant |
P14736
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ampelocera, isVascularPlant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVascularPlant Context triple: [Ampelocera, isVascularPlant, true]
-
A.
hasVascularTissue
chosen
Indicates that an entity possesses specialized vascular tissues (such as xylem and phloem) for internal transport of fluids and nutrients.
-
B.
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).
-
C.
photosyntheticOrganism
Indicates that an organism performs photosynthesis, converting light energy into chemical energy to sustain itself.
-
D.
plantKingdom
Indicates that the subject belongs to, or is classified within, the plant kingdom.
-
E.
hasSporophyteMorphology
Indicates that an entity exhibits the structural form or physical characteristics typical of a sporophyte stage in its life cycle.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c28f5b988190b0be4504eabb919d |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.