Triple
T34615575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herning Kunstmuseum |
E888853
|
entity |
| Predicate | roleTakenOverBy |
P127595
|
FINISHED |
| Object | HEART Herning Museum of Contemporary Art |
—
|
NE NERFINISHED |
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: HEART Herning Museum of Contemporary Art | Statement: [Herning Kunstmuseum, roleTakenOverBy, HEART Herning Museum of Contemporary Art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleTakenOverBy Context triple: [Herning Kunstmuseum, roleTakenOverBy, HEART Herning Museum of Contemporary Art]
-
A.
roleTakenOverFrom
Indicates that one entity has assumed or inherited a role or position that was previously held by another entity.
-
B.
roleReplacedOn
Indicates that one role has been substituted or taken over by another role at a specific point in time.
-
C.
organizationSuccessor
chosen
Indicates that one organization is the direct successor or continuation of another organization, inheriting its role, functions, or identity over time.
-
D.
takenBy
Indicates that something is captured, acquired, or received by a particular entity.
-
E.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.