Triple
T14309203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noratus Cemetery |
E354777
|
entity |
| Predicate | hasKhachkarsFrom |
P38612
|
FINISHED |
| Object | 10th 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: 10th century | Statement: [Noratus Cemetery, hasKhachkarsFrom, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKhachkarsFrom Context triple: [Noratus Cemetery, hasKhachkarsFrom, 10th century]
-
A.
hasRockCarvingsFrom
chosen
Indicates that something contains or features rock carvings that originate from a specified source, place, or period.
-
B.
hasCarvings
Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
-
C.
hasBackCarvings
Indicates that an entity possesses carvings or engraved markings specifically located on its back.
-
D.
hasRootCarvings
Indicates that an object, typically a plant or tree, possesses carvings or engraved markings on its roots.
-
E.
hasIconostasis
Indicates that a place of worship contains or is equipped with an iconostasis, a partition or screen bearing icons that separates different liturgical spaces.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b26da48190a96e2f60ace51335 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.