Triple
T22379347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | parish of Gassel |
E553228
|
entity |
| Predicate | buildingMaterialOfChurch |
P134857
|
FINISHED |
| Object | brick |
—
|
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: brick | Statement: [parish of Gassel, buildingMaterialOfChurch, brick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingMaterialOfChurch Context triple: [parish of Gassel, buildingMaterialOfChurch, brick]
-
A.
parishChurchConstructionMaterial
chosen
Indicates the material from which a parish church is constructed.
-
B.
materialOfChapelRuins
Indicates that a specified material was used in the construction of the chapel whose remains or ruins are being described.
-
C.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
-
D.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
-
E.
hasArchitecturalMaterial
Indicates that something is constructed from, incorporates, or is characterized by a particular architectural material.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582afe6c819093940f9d817c64a8 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.