Triple
T7811630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granary Burial Ground |
E180696
|
entity |
| Predicate | hasOldestGravestonesFrom |
P39958
|
FINISHED |
| Object | 1660s |
—
|
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: 1660s | Statement: [Granary Burial Ground, hasOldestGravestonesFrom, 1660s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldestGravestonesFrom Context triple: [Granary Burial Ground, hasOldestGravestonesFrom, 1660s]
-
A.
eraOfMostBurials
Indicates the historical time period during which the greatest number of burials occurred for a given site or context.
-
B.
oneOfOldestCemeteriesIn
Indicates that a cemetery is among the oldest cemeteries located within a specified place or region.
-
C.
oneOfTheOldestOn
Indicates that one entity is among the earliest or longest-existing examples within the set defined by another entity.
-
D.
oldestCemeteryIn
Indicates that a cemetery is the most ancient or earliest established burial ground within a specified location or region.
-
E.
usedAsCemeterySince
chosen
Indicates that a place has functioned as a cemetery starting from a specified point in time.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78cd1cc8190b4cdd9850e1e2bb7 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:37 p.m.