Triple
T18596779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dokk1 |
E454511
|
entity |
| Predicate | GongSculptureFunction |
P116585
|
FINISHED |
| Object | bell rung when a child is born in Aarhus |
—
|
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: bell rung when a child is born in Aarhus | Statement: [Dokk1, GongSculptureFunction, bell rung when a child is born in Aarhus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GongSculptureFunction Context triple: [Dokk1, GongSculptureFunction, bell rung when a child is born in Aarhus]
-
A.
usesSculptureFor
chosen
Indicates that one entity employs or utilizes a sculpture for a particular purpose, function, or activity.
-
B.
assistantSculptor
Indicates a relationship where one entity serves as an assistant to another entity in the role or activity of sculpting.
-
C.
sculpts
Indicates that one entity creates or shapes another entity by carving or modeling a material into a desired form.
-
D.
featuresSculptureOf
Indicates that one entity includes or displays a sculpture that depicts or represents another entity.
-
E.
sculpturalProgramDesignedBy
Indicates that a sculptural program was conceived, planned, or created by a particular designer or artist.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474ce0c08190b440cbe86b6ef7b9 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.