Triple
T583752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of Amsterdam |
E15111
|
entity |
| Predicate | reasonForEstablishment |
P5256
|
FINISHED |
| Object | to stabilize chaotic coinage |
—
|
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: to stabilize chaotic coinage | Statement: [Bank of Amsterdam, reasonForEstablishment, to stabilize chaotic coinage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEstablishment Context triple: [Bank of Amsterdam, reasonForEstablishment, to stabilize chaotic coinage]
-
A.
reasonForCreation
chosen
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
B.
foundedAsResultOf
Indicates that one entity was established or created as a direct consequence or outcome of another event, action, or circumstance.
-
C.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
D.
foundedOnOccasionOf
Indicates that something was established or created specifically in response to, or to mark, a particular event or occasion.
-
E.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b8745c88190af9672e5fe8396c3 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c9315c8190a773e8e00737d8a0 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.