Triple
T33462337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cimetière de Perpignan |
E856951
|
entity |
| Predicate | hasBurialRightType |
P47508
|
FINISHED |
| Object | individual graves |
—
|
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: individual graves | Statement: [Cimetière de Perpignan, hasBurialRightType, individual graves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialRightType Context triple: [Cimetière de Perpignan, hasBurialRightType, individual graves]
-
A.
hasBurialGoodType
Indicates that a burial includes or is associated with a specific type or category of burial good.
-
B.
hasBurialEligibility
chosen
Indicates that one entity is permitted or qualified to be buried in a particular place, context, or under specified conditions.
-
C.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
D.
hasBurialRestriction
Indicates that there is a rule, condition, or limitation governing how, where, or whether a burial may take place.
-
E.
hasBuriedPersonRole
Indicates that an entity plays a specific role in the context of a person who has been buried (e.g., as the buried individual or in relation to the burial).
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:37 a.m.