Triple
T24857505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleph |
E622066
|
entity |
| Predicate | abjadNumericValue |
P44433
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Aleph, abjadNumericValue, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abjadNumericValue Context triple: [Aleph, abjadNumericValue, 1]
-
A.
hasAbjadValue
chosen
Indicates that a symbol or character is associated with a specific numerical value according to an abjad (letter–number) system.
-
B.
numericValueInGematria
Indicates that a given entity is associated with a specific numerical value as determined by the rules of gematria.
-
C.
alphabeticPosition
Indicates the relative position of a character or letter within an ordered alphabet sequence.
-
D.
numericValueInIsopsephy
Indicates that a given entity has a specific numerical value when calculated according to the rules of isopsephy (the Greek letter-to-number system).
-
E.
numericalValueInGematria
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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:21 a.m.