Triple
T20040434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point of Graves Burial Ground |
E497398
|
entity |
| Predicate | hasMaterialOfStones |
P138464
|
FINISHED |
| Object | slate |
—
|
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: slate | Statement: [Point of Graves Burial Ground, hasMaterialOfStones, slate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialOfStones Context triple: [Point of Graves Burial Ground, hasMaterialOfStones, slate]
-
A.
hasRegionalStone
Indicates that something possesses or is associated with a characteristic stone specific to a particular region.
-
B.
hasCentralStoneType
Indicates that an item, typically a piece of jewelry, features a central stone of a specified type.
-
C.
usesOriginalStones
Indicates that something is constructed or preserved using the same stones that were part of the original structure or artifact.
-
D.
casingStonesPresent
Indicates that the outer protective or decorative casing stones are present on a structure or object.
-
E.
suppliedStoneTo
Indicates that one entity provided or delivered stone materials to another entity.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662eae538819083c74d7a2ab493d2 |
completed | April 20, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:36 p.m.