Triple
T29522230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capela dos Ossos |
E748965
|
entity |
| Predicate | sourceOfBones |
P94432
|
FINISHED |
| Object | local cemeteries in Évora |
—
|
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: local cemeteries in Évora | Statement: [Capela dos Ossos, sourceOfBones, local cemeteries in Évora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfBones Context triple: [Capela dos Ossos, sourceOfBones, local cemeteries in Évora]
-
A.
skeleton
Indicates that one entity serves as the basic structural framework or underlying support for another.
-
B.
numberOfBonesRecovered
Indicates the count of bones that have been found and recovered in relation to a particular subject or event.
-
C.
المنشأ
chosen
Indicates the origin or source from which an entity, action, or relationship arises or is derived.
-
D.
firstTransferOfBones
Indicates the initial instance in which a set of bones is moved or handed over from one party or location to another.
-
E.
interpretationOfBones
Indicates the act of analyzing and deriving meaning or conclusions from bones, such as for medical, archaeological, or forensic purposes.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 4:42 p.m.