Triple
T27496808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strobilanthes kunthiana |
E694038
|
entity |
| Predicate | seedProduction |
P129018
|
FINISHED |
| Object | abundant after mass flowering |
—
|
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: abundant after mass flowering | Statement: [Strobilanthes kunthiana, seedProduction, abundant after mass flowering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seedProduction Context triple: [Strobilanthes kunthiana, seedProduction, abundant after mass flowering]
-
A.
seedProduct
Indicates that one entity serves as the original or source product from which another related product is derived or initialized.
-
B.
seedEnclosure
Indicates that one entity serves as a container or protective space in which another entity’s seeds are held or stored.
-
C.
seedType
Indicates the specific kind or category of seed associated with an entity.
-
D.
seedMass
Indicates the mass or weight associated with a seed in the relationship.
-
E.
plantProduces
chosen
Indicates that a plant generates, creates, or yields a particular substance, structure, or product as a result of its biological processes.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ec0087c819092b5a19c4bf6a3d0 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:09 p.m.