Triple
T11103644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Chapel Cemetery, Millwood, Virginia |
E262571
|
entity |
| Predicate | hasTypeOfGravestones |
P42243
|
FINISHED |
| Object | historic grave markers |
—
|
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: historic grave markers | Statement: [Old Chapel Cemetery, Millwood, Virginia, hasTypeOfGravestones, historic grave markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfGravestones Context triple: [Old Chapel Cemetery, Millwood, Virginia, hasTypeOfGravestones, historic grave markers]
-
A.
hasTypeOfGrave
chosen
Indicates that an entity is associated with a specific kind or category of grave.
-
B.
hasGravestoneStyle
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
-
C.
hasGravestone
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
D.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
E.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a2d33948190ac29d174694a78e5 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.