Triple
T31363278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish cemetery in Kolín |
E799936
|
entity |
| Predicate | hasEarliestGraves |
P25897
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [Jewish cemetery in Kolín, hasEarliestGraves, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarliestGraves Context triple: [Jewish cemetery in Kolín, hasEarliestGraves, medieval period]
-
A.
earliestBurials
chosen
Indicates that the referenced burials are among the first or oldest known interments associated with a given site, group, or context.
-
B.
isOneOfEarliestTombsIn
Indicates that a tomb belongs to the earliest group of tombs known or constructed within a specified place or context.
-
C.
eraOfMostBurials
Indicates the historical time period during which the greatest number of burials occurred for a given site or context.
-
D.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
E.
earliestCultEvidence
Indicates the earliest known archaeological or historical evidence for the existence of a particular cult or organized worship practice.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f81b5a48190905c819d68aea499 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:18 p.m.