Triple
T25848104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eshel Avraham |
E651126
|
entity |
| Predicate | placeInPriMegadim |
P42883
|
FINISHED |
| Object | commentary on Orach Chaim |
—
|
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: commentary on Orach Chaim | Statement: [Eshel Avraham, placeInPriMegadim, commentary on Orach Chaim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInPriMegadim Context triple: [Eshel Avraham, placeInPriMegadim, commentary on Orach Chaim]
-
A.
designedToPlace
Indicates that something is intentionally created or configured for the purpose of positioning or setting another entity in a specific place or arrangement.
-
B.
placementIn
chosen
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
C.
meetsInPlaceOf
Indicates that one entity meets or comes together with another specifically at a designated place or location.
-
D.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
E.
centralPlinthHeight
Indicates the height of a central plinth relative to a defined reference or surrounding elements.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 22, 2026, 7:57 a.m.