Triple
T25819753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fischerhude |
E650367
|
entity |
| Predicate | artistsColonyFlourishedIn |
P16598
|
FINISHED |
| Object | early 20th 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: early 20th century | Statement: [Fischerhude, artistsColonyFlourishedIn, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artistsColonyFlourishedIn Context triple: [Fischerhude, artistsColonyFlourishedIn, early 20th century]
-
A.
flourishedAmong
Indicates that an entity thrived, prospered, or reached a peak of development within a particular group, environment, or context.
-
B.
flourishedIn
chosen
Indicates that an entity experienced its peak activity, success, or prominence during a specified time period or era.
-
C.
locatedInSettlementFoundedBy
Indicates that something is located in a settlement that was founded by a specified entity.
-
D.
regionOfColonyFounded
Indicates the geographic region in which a particular colony was originally founded.
-
E.
colonyFoundedBy
Indicates that a particular colony was established or created by a specific founding entity (such as a person, group, or organization).
- 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_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 7:28 a.m.