Triple
T35692910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willingshausen |
E1031348
|
entity |
| Predicate | hasArtistsColonySince |
P145906
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Willingshausen, hasArtistsColonySince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistsColonySince Context triple: [Willingshausen, hasArtistsColonySince, 19th century]
-
A.
hasResidentArtist
Indicates that one entity serves as the resident artist associated with or based at another entity.
-
B.
hasArtColonyHistory
chosen
Indicates that an entity has a historical association with an art colony, such as having hosted, contained, or been significantly involved with one.
-
C.
hasSiblingArtists
Indicates that the entities are siblings who are both artists or involved in artistic professions.
-
D.
hasArtCentreEstablishedFor
Indicates that an art centre has been created or set up specifically for the benefit, use, or service of a particular entity.
-
E.
hasArtisticAssociationWith
Indicates a relationship in which two entities are connected through shared, collaborative, or thematically related artistic work or influence.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 3, 2026, 4:05 p.m.