Triple
T29297974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flagellariaceae |
E742882
|
entity |
| Predicate | leafApexFunction |
P166947
|
FINISHED |
| Object | climbing tendril |
—
|
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: climbing tendril | Statement: [Flagellariaceae, leafApexFunction, climbing tendril]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leafApexFunction Context triple: [Flagellariaceae, leafApexFunction, climbing tendril]
-
A.
leafFunction
Indicates that something serves as a terminal or non-decomposable function within a larger functional or computational structure.
-
B.
apexOf
Indicates that one entity is the highest or most extreme point, level, or culmination of another entity or process.
-
C.
apexFor
Indicates that one entity serves as the highest point, culmination, or peak state for another entity or process.
-
D.
leafPosition
Indicates the spatial or structural placement of a leaf relative to its supporting plant organ or axis.
-
E.
leafType
Indicates the specific kind or classification of leaf associated with an entity.
- F. None of above. chosen
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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6654594048190ad15dbcd2c16db2e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 1:08 p.m.