Triple
T11549158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muehlenbeckia |
E273845
|
entity |
| Predicate | hasStemCharacteristic |
P21056
|
FINISHED |
| Object | slender wiry stems |
—
|
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: slender wiry stems | Statement: [Muehlenbeckia, hasStemCharacteristic, slender wiry stems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStemCharacteristic Context triple: [Muehlenbeckia, hasStemCharacteristic, slender wiry stems]
-
A.
hasStem
Indicates that one entity possesses or is characterized by a stem as a structural or functional part.
-
B.
stemType
chosen
Indicates the type or form of a stem that an entity possesses or is characterized by.
-
C.
hasStomata
Indicates that an entity possesses stomata, meaning it has the microscopic pores or openings typically used for gas exchange.
-
D.
hasSporophyteCharacteristic
Indicates that an entity possesses a characteristic or trait associated with the sporophyte stage of a life cycle.
-
E.
tailCharacteristic
Indicates that an entity possesses a particular property, feature, or quality specifically related to its tail.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e615b08190a072924329a94a6a |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087e57b48190a4c253dc0210f9d4 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.