Triple
T4868457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaar Hashomayim Cemetery |
E109026
|
entity |
| Predicate | hasGraveMarkerType |
P22905
|
FINISHED |
| Object | headstones |
—
|
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: headstones | Statement: [Shaar Hashomayim Cemetery, hasGraveMarkerType, headstones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGraveMarkerType Context triple: [Shaar Hashomayim Cemetery, hasGraveMarkerType, headstones]
-
A.
hasTypeOfGrave
Indicates that an entity is associated with a specific kind or category of grave.
-
B.
hasGravestone
chosen
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
C.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
D.
hasGravestoneStyle
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
-
E.
hasCemeteryType
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7d809081909fc7c80c56f72840 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.