Triple
T21592510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviathan |
E532814
|
entity |
| Predicate | canBeSubduedBy |
P144085
|
FINISHED |
| Object | God alone |
—
|
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: God alone | Statement: [Leviathan, canBeSubduedBy, God alone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSubduedBy Context triple: [Leviathan, canBeSubduedBy, God alone]
-
A.
isAttenuated
Indicates that the strength, intensity, or effect of something has been reduced or weakened relative to a prior or normal state.
-
B.
canBeDisturbedBy
Indicates that an entity is susceptible to being interrupted, bothered, or otherwise negatively affected by another entity or factor.
-
C.
canBeDeactivatedBy
Indicates that one entity has the ability or means to deactivate or disable 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.
canBeDisabledOn
Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefadeb56c8190bce79efadf3c644d |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63384a8fc819084c596bb53a3a1db |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 16, 2026, 6:32 p.m.