Triple
T25819752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fischerhude |
E650367
|
entity |
| Predicate | developedAsArtistsColonyIn |
P104718
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Fischerhude, developedAsArtistsColonyIn, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAsArtistsColonyIn Context triple: [Fischerhude, developedAsArtistsColonyIn, late 19th century]
-
A.
artistResidence
Indicates that a given location is the place where an artist lives or is based.
-
B.
foundedAsArtistsVillage
chosen
Indicates that a place or settlement was originally established with the primary purpose of serving as a community or village for artists.
-
C.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
D.
colonyOf
Indicates that one entity is a colony belonging to, founded by, or politically dependent on another entity.
-
E.
developedUnderAuspicesOf
Indicates that something was developed under the sponsorship, guidance, or official authority of a particular organization or 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 7:28 a.m.