Triple
T11843332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morne-à-l’Eau |
E281707
|
entity |
| Predicate | cemeteryStyle |
P101810
|
FINISHED |
| Object | checkerboard pattern tombs |
—
|
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: checkerboard pattern tombs | Statement: [Morne-à-l’Eau, cemeteryStyle, checkerboard pattern tombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteryStyle Context triple: [Morne-à-l’Eau, cemeteryStyle, checkerboard pattern tombs]
-
A.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
B.
cemeteryComplex
Indicates a relationship where a site or structure functions as, or is part of, a cemetery complex used for burials or memorials.
-
C.
cemeterySection
Indicates that one entity is a specific section, area, or subdivision within a cemetery associated with the other entity.
-
D.
hasGravestoneStyle
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
-
E.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65a597c8190b09f57463b279afc |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.