Triple
T16795711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igreja do Carmo (Faro) |
E408224
|
entity |
| Predicate | hasCemeteryFeature |
P124662
|
FINISHED |
| Object | ossuary |
—
|
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: ossuary | Statement: [Igreja do Carmo (Faro), hasCemeteryFeature, ossuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCemeteryFeature Context triple: [Igreja do Carmo (Faro), hasCemeteryFeature, ossuary]
-
A.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
B.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
C.
hasCemeteryType
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
-
D.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
E.
cemeteryCapacitySupported
Indicates that an entity provides or supports the necessary capacity (such as space or resources) for a cemetery to operate or accommodate burials.
- F. None of above. chosen
Provenance (4 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a96d888190a9876c3784bb7f95 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.