Triple
T33880011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish community of Nevis |
E868457
|
entity |
| Predicate | cemeteryNotableFeature |
P64621
|
FINISHED |
| Object | Hebrew-inscribed tombstones |
—
|
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: Hebrew-inscribed tombstones | Statement: [Jewish community of Nevis, cemeteryNotableFeature, Hebrew-inscribed tombstones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteryNotableFeature Context triple: [Jewish community of Nevis, cemeteryNotableFeature, Hebrew-inscribed tombstones]
-
A.
cemeteryKnownFor
chosen
Indicates that a cemetery is notable or recognized for a particular person, event, feature, or characteristic.
-
B.
tombNotableFeature
Indicates that a tomb is distinguished or recognized for a particular notable feature or characteristic.
-
C.
hasCemeteryFeature
Indicates that a cemetery possesses or is characterized by a specific feature or attribute.
-
D.
hasChurchyardFeature
Indicates that a churchyard possesses or includes a particular physical or functional feature.
-
E.
cemeteryComplex
Indicates a relationship where a site or structure functions as, or is part of, a cemetery complex used for burials or memorials.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.