Triple
T36786241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesser YHWH |
E908919
|
entity |
| Predicate | impliesHierarchyWith |
P41995
|
FINISHED |
| Object | God |
—
|
NE NERFINISHED |
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 | Statement: [Lesser YHWH, impliesHierarchyWith, God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesHierarchyWith Context triple: [Lesser YHWH, impliesHierarchyWith, God]
-
A.
hasHierarchyIn
chosen
Indicates that one entity occupies a higher or lower level within an ordered structure or chain of command relative to another entity in a specified context.
-
B.
isPartOfHierarchyWith
Indicates that one entity occupies a defined position within an ordered or nested structure relative to another entity in the same hierarchy.
-
C.
impliesLineage
Indicates that one entity is inferred to be ancestrally or genealogically derived from another.
-
D.
hasHierarchyAbove
Indicates that one entity occupies a higher or superior level in an ordered structure or chain of command relative to another entity.
-
E.
preservesOwnHierarchy
Indicates that an entity maintains and does not alter the structural hierarchy of its own internal components or organization.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.