Triple
T22231848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family chapel at Doughoregan Manor, Maryland |
E549485
|
entity |
| Predicate | burialSiteFor |
P196
|
FINISHED |
| Object | members of the Carroll family |
—
|
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: members of the Carroll family | Statement: [Family chapel at Doughoregan Manor, Maryland, burialSiteFor, members of the Carroll family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialSiteFor Context triple: [Family chapel at Doughoregan Manor, Maryland, burialSiteFor, members of the Carroll family]
-
A.
burialSiteNear
Indicates that the burial site of one entity is located geographically close to another entity.
-
B.
burialPlace
chosen
Indicates the location where a person or entity is buried.
-
C.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
D.
reputedBurialPlaceOf
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
E.
burialSiteFeature
Indicates a specific physical characteristic or element associated with a burial site, such as structures, markers, or other notable features present at the place of interment.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf3de648190986a734f19643a8c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.