Triple
T3725069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yod |
E81727
|
entity |
| Predicate | isUsedInGematria |
P44930
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yod, isUsedInGematria, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedInGematria Context triple: [Yod, isUsedInGematria, true]
-
A.
hasGematriaUsage
chosen
Indicates that something is used or interpreted according to the principles or practices of gematria (assigning numerical values to letters or words).
-
B.
numericalValueInGematria
Indicates that a given entity is associated with a specific numerical value as determined by a gematria system of letter-to-number conversion.
-
C.
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.
-
D.
numericValueInGematria
Indicates that a given entity is associated with a specific numerical value as determined by the rules of gematria.
-
E.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf54af881908bd8d520595de061 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.