Triple
T30993564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boothill Graveyard |
E789731
|
entity |
| Predicate | hasEpitaphStyle |
P11281
|
FINISHED |
| Object | short narrative inscriptions |
—
|
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: short narrative inscriptions | Statement: [Boothill Graveyard, hasEpitaphStyle, short narrative inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpitaphStyle Context triple: [Boothill Graveyard, hasEpitaphStyle, short narrative inscriptions]
-
A.
hasEpitaph
Indicates that an entity has a specific epitaph inscribed or associated with it.
-
B.
hasPoeticEpigraphs
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
-
C.
hasEpitomeBy
Indicates that something is represented, summarized, or exemplified by a particular epitome (a concise or quintessential representation of it).
-
D.
hasGravestoneStyle
chosen
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
-
E.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:56 p.m.