Triple
T21592511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leviathan |
E532814
|
entity |
| Predicate | cannotBeSubduedBy |
P138912
|
FINISHED |
| Object | humans |
—
|
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: humans | Statement: [Leviathan, cannotBeSubduedBy, humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeSubduedBy Context triple: [Leviathan, cannotBeSubduedBy, humans]
-
A.
cannotBeEasilyDisabled
Indicates that the relationship or mechanism cannot be turned off, bypassed, or neutralized without significant effort, expertise, or resources.
-
B.
cannotBeDefeatedBy
chosen
Indicates that one entity is invulnerable to defeat by another specified entity or set of entities.
-
C.
canBeDisturbedBy
Indicates that an entity is susceptible to being interrupted, bothered, or otherwise negatively affected by another entity or factor.
-
D.
cannotBeRemovedBy
Indicates that one entity is not capable of removing, deleting, or otherwise eliminating another entity.
-
E.
notSubordinateTo
Indicates that one entity is not in a lower-ranking, subordinate, or reporting position to another entity within a hierarchy or organizational structure.
- 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_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. |
Created at: April 16, 2026, 6:32 p.m.