Triple
T4333488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motal |
E97407
|
entity |
| Predicate | hasJewishCemetery |
P1496
|
FINISHED |
| Object | Motal Jewish cemetery |
—
|
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: Motal Jewish cemetery | Statement: [Motal, hasJewishCemetery, Motal Jewish cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJewishCemetery Context triple: [Motal, hasJewishCemetery, Motal Jewish cemetery]
-
A.
hasCemetery
chosen
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
B.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
C.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
D.
isPublicCemetery
Indicates that a cemetery is designated, maintained, or recognized as a public burial ground accessible for general community use.
-
E.
hasJewishInstitution
Indicates that a place, organization, or entity possesses, hosts, or is associated with a Jewish religious, cultural, or educational institution.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514faaac819081475681fd10da24 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.