Triple
T19864164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atik (ancient) |
E477343
|
entity |
| Predicate | locatedInHierarchy |
P21686
|
FINISHED |
| Object | highest sefirah |
—
|
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: highest sefirah | Statement: [Atik (ancient), locatedInHierarchy, highest sefirah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHierarchy Context triple: [Atik (ancient), locatedInHierarchy, highest sefirah]
-
A.
isPartOfHierarchyWith
chosen
Indicates that one entity occupies a defined position within an ordered or nested structure relative to another entity in the same hierarchy.
-
B.
hasHierarchyIn
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.
-
C.
positionInHierarchy
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
locatedInOrganizationally
Indicates that one entity is organizationally situated within, or belongs to, another entity in terms of administrative or structural hierarchy.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6589d55a88190af7d4e12c4b07739 |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.