Triple
T19265535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | parish church of Varennes-en-Argonne |
E481765
|
entity |
| Predicate | architecturalClassification |
P4631
|
FINISHED |
| Object | church architecture |
—
|
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: church architecture | Statement: [parish church of Varennes-en-Argonne, architecturalClassification, church architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalClassification Context triple: [parish church of Varennes-en-Argonne, architecturalClassification, church architecture]
-
A.
architectureType
chosen
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
B.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
C.
architecturalWorkType
Indicates the specific kind or category of architectural work that characterizes the relationship between entities.
-
D.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
E.
architecturalFocus
Indicates that something is the primary subject, theme, or area of emphasis within the domain of architecture.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8ca2e88190baad3b6c199ee036 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.