Triple
T19070746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kerameikos |
E466783
|
entity |
| Predicate | timeInUseAsCemetery |
P39958
|
FINISHED |
| Object | from at least the 12th century BCE |
—
|
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: from at least the 12th century BCE | Statement: [Kerameikos, timeInUseAsCemetery, from at least the 12th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInUseAsCemetery Context triple: [Kerameikos, timeInUseAsCemetery, from at least the 12th century BCE]
-
A.
usedAsCemeterySince
chosen
Indicates that a place has functioned as a cemetery starting from a specified point in time.
-
B.
hasNotablePeriodOfUseAsCemetery
Indicates that something was significantly used as a cemetery during a particular period of time.
-
C.
timePeriodOfBurials
Indicates the span of time during which the burials associated with an entity took place.
-
D.
usedAsGraveUntil
Indicates that something continued to function or be designated as a grave up to a specified point in time.
-
E.
usedAsBurialGroundUntil
Indicates that a place functioned as a burial ground up to a specified end time or date.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19ea01c8190b9bb789da32f9a90 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.