Triple
T14697387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beloved (infant daughter) |
E345198
|
entity |
| Predicate | burialInscription |
P57501
|
FINISHED |
| Object | Beloved |
—
|
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: Beloved | Statement: [Beloved (infant daughter), burialInscription, Beloved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialInscription Context triple: [Beloved (infant daughter), burialInscription, Beloved]
-
A.
hasGraveInscription
chosen
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
B.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
E.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58855e081908b38f9515db5677f |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.