Triple
T1404787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian forint |
E31665
|
entity |
| Predicate | usedInFormerEasternBlocCountry |
P27629
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hungarian forint, usedInFormerEasternBlocCountry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFormerEasternBlocCountry Context triple: [Hungarian forint, usedInFormerEasternBlocCountry, true]
-
A.
establishedAsSocialistState
Indicates that an entity formally created or declared another entity to be a socialist state as its system of governance.
-
B.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
-
C.
roleInUSSRDisintegration
Indicates involvement or contribution of an entity to the political, economic, or social processes that led to the disintegration of the USSR.
-
D.
countryAfter1991
Indicates that the entity is recognized as a country that came into existence or gained its current sovereign status after the year 1991.
-
E.
usedInCountry
Indicates that something is utilized, applied, or in operation within the specified country.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.