Triple
T31088915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Cemetery |
E792327
|
entity |
| Predicate | spatiallyRelatedTo |
P17188
|
FINISHED |
| Object | East Cemetery |
—
|
NE NERFINISHED |
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: East Cemetery | Statement: [West Cemetery, spatiallyRelatedTo, East Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spatiallyRelatedTo Context triple: [West Cemetery, spatiallyRelatedTo, East Cemetery]
-
A.
spatialRelation
chosen
Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
-
B.
meetsInRelationTo
Indicates that two or more entities come together or interact within the context of a specified relationship or circumstance.
-
C.
arealRelation
Indicates a spatial relationship between areas, such as overlap, containment, adjacency, or relative positioning between two regions.
-
D.
hasSpatialConcept
Indicates a relationship where one entity is associated with, defined by, or characterized through a particular spatial concept or spatial configuration.
-
E.
spatialRepresentation
Indicates that one entity serves as a spatial depiction, model, or encoding of the location, layout, or geometric properties of 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.