Triple
T23133091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederik Bloemaert |
E577231
|
entity |
| Predicate | primarySourceOfDesigns |
P36679
|
FINISHED |
| Object | Abraham Bloemaert |
—
|
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: Abraham Bloemaert | Statement: [Frederik Bloemaert, primarySourceOfDesigns, Abraham Bloemaert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySourceOfDesigns Context triple: [Frederik Bloemaert, primarySourceOfDesigns, Abraham Bloemaert]
-
A.
designsBy
Indicates that one entity is the creator or designer responsible for the conception or design of another entity.
-
B.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
C.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
D.
hasDesignOrigin
chosen
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
E.
visualDesignInspiredBy
Indicates that the visual design of one entity is influenced, modeled, or derived from the visual style or appearance of 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e89cce881908727a94dbc00e031 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.