Triple
T31363279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish cemetery in Kolín |
E799936
|
entity |
| Predicate | hasLatestGraves |
P196250
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Jewish cemetery in Kolín, hasLatestGraves, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatestGraves Context triple: [Jewish cemetery in Kolín, hasLatestGraves, 20th century]
-
A.
hasGravesFrom
Indicates that a location or site contains graves originating from or associated with a specified source place or group.
-
B.
hasGraves
Indicates that an entity possesses, contains, or is associated with one or more graves.
-
C.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
D.
hasGraveOccupant
Indicates that a grave is occupied by a specific person or entity.
-
E.
hasGravestone
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fe189f2ea48190b8c4718f1353970e |
completed | May 8, 2026, 5:08 p.m. |
Created at: April 29, 2026, 9:18 p.m.