Triple
T28332844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cimetière des Innocents |
E717579
|
entity |
| Predicate | bonesTransferredTo |
P164286
|
FINISHED |
| Object | Paris Catacombs |
—
|
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: Paris Catacombs | Statement: [Cimetière des Innocents, bonesTransferredTo, Paris Catacombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bonesTransferredTo Context triple: [Cimetière des Innocents, bonesTransferredTo, Paris Catacombs]
-
A.
firstTransferOfBones
Indicates the initial instance in which a set of bones is moved or handed over from one party or location to another.
-
B.
bodiesMovedTo
Indicates that one or more physical bodies have been relocated from their original position to a new location.
-
C.
transferredUnder
Indicates that something is moved, conveyed, or reassigned from one party, context, or control to another under specified terms or conditions.
-
D.
transferredWith
Indicates that something was moved or conveyed from one entity to another using a specified medium, method, or accompanying item.
-
E.
someUnitsTransferredTo
Indicates that a certain quantity of units has been moved or reassigned from one entity to another.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64bd3109c81909e5b0d37584b8505 |
completed | May 2, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 28, 2026, 12:33 a.m.