Triple
T37463107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherazin, Corpse Flower |
E930966
|
entity |
| Predicate | canBeSilenced |
P180774
|
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, canBeSilenced, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSilenced Context triple: [Sherazin, Corpse Flower, canBeSilenced, true]
-
A.
canBeSubduedBy
Indicates that one entity is capable of overpowering, restraining, or otherwise bringing another entity under control.
-
B.
canBeSuppressed
chosen
Indicates that the occurrence, effect, or expression of one entity can be reduced, inhibited, or prevented by another.
-
C.
canBeSuppressedBy
Indicates that one entity has the ability to reduce, inhibit, or nullify the effect, presence, or activity of another entity.
-
D.
canSuppress
Indicates that one entity has the ability or capacity to prevent, inhibit, or reduce the effect, activity, or expression of another entity or process.
-
E.
isSilentExceptFor
Indicates that an entity produces no sound or noise except under specific conditions or in certain contexts.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: May 3, 2026, 4:17 p.m.