Triple
T36353786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herzogliches Museum art collection |
E895282
|
entity |
| Predicate | originallyAssembledBy |
P204837
|
FINISHED |
| Object | Dukes of Saxe-Gotha-Altenburg |
E1927783
|
NE 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: Dukes of Saxe-Gotha-Altenburg | Statement: [Herzogliches Museum art collection, originallyAssembledBy, Dukes of Saxe-Gotha-Altenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyAssembledBy Context triple: [Herzogliches Museum art collection, originallyAssembledBy, Dukes of Saxe-Gotha-Altenburg]
-
A.
originallyBuiltBy
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
B.
assembledAt
Indicates that one entity was put together or constructed at a specific location or facility.
-
C.
manufacturedBy
Indicates that an item or product is produced or created by a specific manufacturer or maker.
-
D.
formerManufacturer
Indicates that an entity previously manufactured another entity but no longer does so.
-
E.
engineeredBy
Indicates that an entity has been designed, created, or developed through the technical work or expertise of another entity.
- F. None of above. chosen
Provenance (5 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39a32c17148190a5b1e2dc959a304d |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.