Triple
T28302087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadhuis van Maastricht |
E713735
|
entity |
| Predicate | hasBellFoundry |
P173244
|
FINISHED |
| Object | bells cast by various founders over time |
—
|
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: bells cast by various founders over time | Statement: [Stadhuis van Maastricht, hasBellFoundry, bells cast by various founders over time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBellFoundry Context triple: [Stadhuis van Maastricht, hasBellFoundry, bells cast by various founders over time]
-
A.
bellFoundry
Indicates that an entity operates as a foundry where bells are manufactured or cast.
-
B.
hasBellChamber
Indicates that an entity possesses or includes a bell chamber as one of its structural or functional components.
-
C.
bellfounder
Indicates the role or activity of making, casting, or founding bells.
-
D.
hasBellTower
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
-
E.
hasBells
Indicates that an entity possesses or is equipped with one or more bells.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 11:35 p.m.