Triple
T19833550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam print and map workshops |
E476523
|
entity |
| Predicate | hadClient |
P734
|
FINISHED |
| Object | merchants |
—
|
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: merchants | Statement: [Amsterdam print and map workshops, hadClient, merchants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadClient Context triple: [Amsterdam print and map workshops, hadClient, merchants]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
C.
hasClient
chosen
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
D.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
E.
hadBase
Indicates that an entity maintained or operated from a particular base location or primary site.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656d0347c8190b586c7fe01b61e97 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.