Triple
T5653685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wordsworth’s grave |
E124564
|
entity |
| Predicate | hasGraveyardType |
P2743
|
FINISHED |
| Object | churchyard |
—
|
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: churchyard | Statement: [Wordsworth’s grave, hasGraveyardType, churchyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGraveyardType Context triple: [Wordsworth’s grave, hasGraveyardType, churchyard]
-
A.
hasTypeOfGrave
Indicates that an entity is associated with a specific kind or category of grave.
-
B.
hasCemeteryType
chosen
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
-
C.
hasGravesFrom
Indicates that a location or site contains graves originating from or associated with a specified source place or group.
-
D.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
E.
hasGraveMarkerShape
Indicates that one entity (a grave or burial site) has a grave marker whose physical form or outline matches the specified shape.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022f7efec8190946c925130176d5a |
completed | March 22, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.