Triple
T32186828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chlorogalum |
E822127
|
entity |
| Predicate | tepalCharacteristic |
P173294
|
FINISHED |
| Object | narrow spreading tepals |
—
|
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: narrow spreading tepals | Statement: [Chlorogalum, tepalCharacteristic, narrow spreading tepals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tepalCharacteristic Context triple: [Chlorogalum, tepalCharacteristic, narrow spreading tepals]
-
A.
pepperCharacteristic
Indicates that a specified characteristic or quality is attributed to a pepper.
-
B.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
C.
artCharacteristics
Indicates a relationship where specific qualities, styles, or features are attributed to a work of art.
-
D.
eraCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
-
E.
characteristicDevice
Indicates that a device is a defining or typical instrument, tool, or equipment associated with a particular entity, context, or activity.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6babadb3481908b49400b3ab42a7c |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:35 a.m.