Triple
T9575729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polygalaceae |
E231040
|
entity |
| Predicate | hasPetalCharacteristic |
P68196
|
FINISHED |
| Object | petals often resembling papilionoid legumes |
—
|
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: petals often resembling papilionoid legumes | Statement: [Polygalaceae, hasPetalCharacteristic, petals often resembling papilionoid legumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPetalCharacteristic Context triple: [Polygalaceae, hasPetalCharacteristic, petals often resembling papilionoid legumes]
-
A.
hasPetalType
Indicates that an entity possesses petals characterized by a specific type or form.
-
B.
hasSpecializedPetal
Indicates that an entity possesses petals that are specialized or modified for a particular function or role.
-
C.
hasFloralFeature
chosen
Indicates that an entity possesses a specific floral characteristic, structure, or attribute.
-
D.
petalCount
Indicates the number of petals associated with an entity, typically a flower or floral structure.
-
E.
hasFlowerColor
Indicates that an entity (typically a plant or flower) possesses a specific flower color.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99aa964c8190a50717edff30f10b |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.