Triple
T2981011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pe |
E80509
|
entity |
| Predicate | numericalValueHebrewGematria |
P44439
|
FINISHED |
| Object | 80 |
—
|
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: 80 | Statement: [Pe, numericalValueHebrewGematria, 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericalValueHebrewGematria Context triple: [Pe, numericalValueHebrewGematria, 80]
-
A.
numericValueInGreekNumerals
Indicates that a given numeric value is represented or expressed using Greek numeral notation.
-
B.
numberInBiblicalText
Indicates that a specific number appears within, or is referenced by, a given passage or unit of biblical text.
-
C.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
-
D.
hasNumericValueInGreekNumerals
Indicates that an entity is associated with a specific numeric value expressed using Greek numeral notation.
-
E.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99a098e08190976eb4b019818f67 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.