Triple
T21869265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cytinaceae |
E539960
|
entity |
| Predicate | commonFeatureOfMembers |
P21536
|
FINISHED |
| Object | emergence only during flowering and fruiting |
—
|
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: emergence only during flowering and fruiting | Statement: [Cytinaceae, commonFeatureOfMembers, emergence only during flowering and fruiting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonFeatureOfMembers Context triple: [Cytinaceae, commonFeatureOfMembers, emergence only during flowering and fruiting]
-
A.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
-
B.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
C.
commonAttribute
chosen
Indicates that two or more entities share the same specified attribute or property.
-
D.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
E.
commonStructure
Indicates that two or more entities share the same or a very similar internal organization, pattern, or arrangement.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f334362c819094af465ee57b47e6 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:57 p.m.