Triple
T2056748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Numbers |
E45690
|
entity |
| Predicate | meaningOfHebrewTitle |
P4542
|
FINISHED |
| Object | in the wilderness |
—
|
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: in the wilderness | Statement: [Book of Numbers, meaningOfHebrewTitle, in the wilderness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfHebrewTitle Context triple: [Book of Numbers, meaningOfHebrewTitle, in the wilderness]
-
A.
titleMeaning
chosen
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
B.
hasNameInHebrew
Indicates that an entity is associated with a specific name expressed in the Hebrew language.
-
C.
nameMeaningInArabic
Indicates that the predicate specifies the meaning or interpretation of a name when expressed in the Arabic language.
-
D.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
E.
hasTitleEtymology
Indicates that the origin or derivation of a title is based on, or explained by, another term, name, or linguistic source.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9abdb088190991a620e01dc226f |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.