Triple
T35874900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | יד אבשלום |
E1037330
|
entity |
| Predicate | סמוך ל |
P183932
|
FINISHED |
| Object | קבר בני חזיר |
—
|
NE NERFINISHED |
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: קבר בני חזיר | Statement: [יד אבשלום, סמוך ל, קבר בני חזיר]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: סמוך ל Context triple: [יד אבשלום, סמוך ל, קבר בני חזיר]
-
A.
possiblyBy
Indicates that an action, creation, or effect may have been caused or produced by a particular entity, but this attribution is uncertain or not definitively established.
-
B.
likelyUse
Indicates that one entity is expected or probable to use, employ, or make use of another entity in a given context.
-
C.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
D.
likelyStatus
Indicates the probable or expected state or condition of an entity based on available information or inference.
-
E.
likelyFuture
Indicates that one entity is predicted or expected to occur, hold, or be true at a future time relative to another reference point or context.
- 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa33e0488190a135166bb67e1118 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.