Triple
T18374739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | church tower of the Church of the Assumption of the Virgin Mary |
E446280
|
entity |
| Predicate | hasBellRinging |
P34829
|
FINISHED |
| Object | manual ringing |
—
|
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: manual ringing | Statement: [church tower of the Church of the Assumption of the Virgin Mary, hasBellRinging, manual ringing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBellRinging Context triple: [church tower of the Church of the Assumption of the Virgin Mary, hasBellRinging, manual ringing]
-
A.
hasBells
Indicates that an entity possesses or is equipped with one or more bells.
-
B.
hasBellChamber
Indicates that an entity possesses or includes a bell chamber as one of its structural or functional components.
-
C.
hasBellWeight
Indicates that an entity (typically a bell) has a specific weight value associated with it.
-
D.
hasChimes
chosen
Indicates that one entity possesses or is equipped with chimes as a feature or component.
-
E.
castBell
Indicates that an entity creates or forms a bell by pouring molten material into a mold or otherwise shaping it.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51757a75c8190814db973ae1a86cd |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.