Triple
T20553320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ana Bekoach |
E504651
|
entity |
| Predicate | numerologicalBasis |
P44430
|
FINISHED |
| Object | 42 letters |
—
|
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: 42 letters | Statement: [Ana Bekoach, numerologicalBasis, 42 letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numerologicalBasis Context triple: [Ana Bekoach, numerologicalBasis, 42 letters]
-
A.
hasNumerology
Indicates a relationship where a numerological value, interpretation, or system is associated with an entity.
-
B.
digitMeaning
Indicates that a particular digit symbol is associated with a specific numerical value or conceptual meaning.
-
C.
numberingSystemBasedOn
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
D.
numericalValueHebrewGematria
Indicates that a numerical value is assigned to text based on Hebrew gematria, where Hebrew letters correspond to specific numbers and their sum yields the value.
-
E.
numericalValueInGematria
chosen
Indicates that a given entity is associated with a specific numerical value as determined by a gematria system of letter-to-number conversion.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5db052c8190801e53f6148113c8 |
completed | April 20, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.