Triple
T36363897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Street Graveyard, Mobile, Alabama |
E895567
|
entity |
| Predicate | usedAsCityCemeteryUntil |
P84274
|
FINISHED |
| Object | 1830s |
—
|
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: 1830s | Statement: [Church Street Graveyard, Mobile, Alabama, usedAsCityCemeteryUntil, 1830s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCityCemeteryUntil Context triple: [Church Street Graveyard, Mobile, Alabama, usedAsCityCemeteryUntil, 1830s]
-
A.
usedAsCemeterySince
Indicates that a place has functioned as a cemetery starting from a specified point in time.
-
B.
usedAsBurialGroundUntil
chosen
Indicates that a place functioned as a burial ground up to a specified end time or date.
-
C.
usedAsGraveUntil
Indicates that something continued to function or be designated as a grave up to a specified point in time.
-
D.
usedAsMainCemeteryOf
Indicates that one location functions as the primary burial ground or principal cemetery serving another entity (such as a settlement, community, or institution).
-
E.
hasNotablePeriodOfUseAsCemetery
Indicates that something was significantly used as a cemetery during a particular period of time.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:10 p.m.