Triple
T29585998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Saint-Jacques-de-la-Boucherie |
E754020
|
entity |
| Predicate | survivingElement |
P167481
|
FINISHED |
| Object | Tour Saint-Jacques |
—
|
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: Tour Saint-Jacques | Statement: [Church of Saint-Jacques-de-la-Boucherie, survivingElement, Tour Saint-Jacques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingElement Context triple: [Church of Saint-Jacques-de-la-Boucherie, survivingElement, Tour Saint-Jacques]
-
A.
survivesBy
Indicates that one entity continues to live or exist after another entity has died or ceased to exist.
-
B.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
C.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
D.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
-
E.
survivedBy
Indicates that one entity continues to live or exist after the death or end of another entity.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7dfb948190b35070cef785d6b8 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:10 p.m.