Triple
T6794711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafayette Cemetery No. 1 |
E156024
|
entity |
| Predicate | cityCemeteryNumber |
P21397
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Lafayette Cemetery No. 1, cityCemeteryNumber, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCemeteryNumber Context triple: [Lafayette Cemetery No. 1, cityCemeteryNumber, 1]
-
A.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
B.
numberOfCemeteries
chosen
Indicates the count of cemeteries associated with a given entity or within a specified area.
-
C.
cemeteryArea
Indicates that an area or region is designated, used, or recognized as a cemetery.
-
D.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
E.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2c59648819081736d27d52d957f |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.