Triple
T19969496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wörgl |
E480031
|
entity |
| Predicate | currencyExperimentStart |
P138070
|
FINISHED |
| Object | 1932 |
—
|
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: 1932 | Statement: [Wörgl, currencyExperimentStart, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyExperimentStart Context triple: [Wörgl, currencyExperimentStart, 1932]
-
A.
currencyExperimentResult
Indicates that a particular outcome or data point was produced as the result of a specific experiment involving currency.
-
B.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
C.
currencyTransition
Indicates a change from one currency to another within a transaction, system, or context.
-
D.
currencyInitiative
Indicates an initiative, program, or action specifically related to the development, regulation, promotion, or reform of a currency or monetary system.
-
E.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc7c2fc81909b89c549a5f99e4c |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.