Triple
T10166292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eta |
E235211
|
entity |
| Predicate | numericValueInIsopsephy |
P92187
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [eta, numericValueInIsopsephy, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericValueInIsopsephy Context triple: [eta, numericValueInIsopsephy, 8]
-
A.
numericValueInGematria
Indicates that a given entity is associated with a specific numerical value as determined by the rules of gematria.
-
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.
numericValueInGreekNumerals
Indicates that a given numeric value is represented or expressed using Greek numeral notation.
-
E.
hasNumericValueInGreekNumerals
Indicates that an entity is associated with a specific numeric value expressed using Greek numeral notation.
- F. None of above. chosen
Provenance (4 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6cf27481909f38839452ac0e37 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.