Triple
T35612431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulcán |
E1029071
|
entity |
| Predicate | hasMunicipalCemetery |
P1496
|
FINISHED |
| Object | Cementerio Municipal de Tulcán |
—
|
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: Cementerio Municipal de Tulcán | Statement: [Tulcán, hasMunicipalCemetery, Cementerio Municipal de Tulcán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalCemetery Context triple: [Tulcán, hasMunicipalCemetery, Cementerio Municipal de Tulcán]
-
A.
hasCemetery
chosen
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
B.
hasMunicipalCemeteryNumber
Indicates that a municipality is associated with a specific identifying number assigned to one of its cemeteries.
-
C.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
D.
hasCemeteryFeature
Indicates that a cemetery possesses or is characterized by a specific feature or attribute.
-
E.
isPublicCemetery
Indicates that a cemetery is designated, maintained, or recognized as a public burial ground accessible for general community use.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.