Triple
T13809013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacques Lemercier |
E331833
|
entity |
| Predicate | architecturalTypeWorkedOn |
P4631
|
FINISHED |
| Object | churches |
—
|
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: churches | Statement: [Jacques Lemercier, architecturalTypeWorkedOn, churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalTypeWorkedOn Context triple: [Jacques Lemercier, architecturalTypeWorkedOn, churches]
-
A.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
B.
architecturalContribution
Indicates a relationship where an entity contributes to the design, planning, or creation of an architectural work or feature.
-
C.
architecturalProject
Indicates that one entity is an architectural project associated with, created by, or undertaken for another entity.
-
D.
architectureType
chosen
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
E.
relatedWorkOfArchitect
Indicates that one work is related to, associated with, or otherwise connected in context or authorship to an architect.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026eae8481908b8880635e6a9152 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.