Triple
T36690504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Or Akiva cemetery |
E905941
|
entity |
| Predicate | hasBurialPlotFor |
P38888
|
FINISHED |
| Object | Ezer Weizman |
—
|
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: Ezer Weizman | Statement: [Or Akiva cemetery, hasBurialPlotFor, Ezer Weizman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialPlotFor Context triple: [Or Akiva cemetery, hasBurialPlotFor, Ezer Weizman]
-
A.
isCemeteryFor
chosen
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
B.
burialPlace
Indicates the location where a person or entity is buried.
-
C.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
D.
hasPartInGrave
Indicates that an entity includes another entity as a physical component or element within a grave.
-
E.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:12 p.m.