Triple
T2099090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch rijksdaalder |
E37051
|
entity |
| Predicate | circulationStart |
P35952
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Dutch rijksdaalder, circulationStart, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulationStart Context triple: [Dutch rijksdaalder, circulationStart, 16th century]
-
A.
circulation
Indicates the movement or flow of something (such as information, materials, or currency) through a system, network, or among entities.
-
B.
circulationStatus
Indicates the current availability or loan state of an item within a circulation or lending system.
-
C.
circulationType
Indicates the manner or category of movement, distribution, or flow associated with the related entities.
-
D.
circulationRole
Indicates the role or function an entity has within a circulation process or system (e.g., how it participates in the movement or flow of something).
-
E.
circulationPeriod
Indicates the length of time during which an item is allowed to be borrowed, used, or remain in active circulation before it must be returned, renewed, or retired.
- F. None of above. chosen
Provenance (4 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbab9f5b88190b8a18056dc592dde |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abba2e65b48190bb19cfc4b0f8c462 |
completed | March 7, 2026, 5:39 a.m. |
Created at: March 4, 2026, 7:43 p.m.