Triple
T37463108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherazin, Corpse Flower |
E930966
|
entity |
| Predicate | canBeTransformed |
P199140
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sherazin, Corpse Flower, canBeTransformed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTransformed Context triple: [Sherazin, Corpse Flower, canBeTransformed, true]
-
A.
canTransform
Indicates that one entity is capable of being changed or converted into another entity or state.
-
B.
usesTransformation
Indicates that one entity applies or relies on a specific transformation process, method, or function to operate on or convert another entity.
-
C.
hasTransformation
Indicates that one entity changes or is converted into another entity, capturing a transformation process or result.
-
D.
wouldTransform
Indicates that one entity has the potential or hypothetical effect of changing, converting, or altering another entity into a different state or form.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
| PDg | Predicate description generation | batch_69ff21ca6964819088bdf1810b7863f2 |
completed | May 9, 2026, noon |
Created at: May 3, 2026, 4:17 p.m.