Triple
T17544672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apodanthaceae |
E427294
|
entity |
| Predicate | emergence |
P122523
|
FINISHED |
| Object | flowers emerge from host stems or branches |
—
|
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: flowers emerge from host stems or branches | Statement: [Apodanthaceae, emergence, flowers emerge from host stems or branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergence Context triple: [Apodanthaceae, emergence, flowers emerge from host stems or branches]
-
A.
modeOfEmergence
chosen
Indicates the manner or process through which something comes into existence, develops, or arises.
-
B.
emergesAs
Indicates that one entity comes to be recognized, develops, or appears in the role, form, or status of another entity over time.
-
C.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
D.
stanceOnEmergence
Indicates a subject’s position, view, or attitude regarding the concept or phenomenon of emergence.
-
E.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e454609bdc8190b81b362906e7e3fd |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.