Triple
T1404783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian forint |
E31665
|
entity |
| Predicate | historicalSubunitInUseUntil |
P8012
|
FINISHED |
| Object | fillér |
—
|
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: fillér | Statement: [Hungarian forint, historicalSubunitInUseUntil, fillér]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSubunitInUseUntil Context triple: [Hungarian forint, historicalSubunitInUseUntil, fillér]
-
A.
historicalSubunit
Indicates that one entity functioned as a subordinate or component part of another entity during a specific historical period, but is no longer in that role in the present.
-
B.
historicalSubunitToUnit
chosen
Indicates that one entity was historically a subunit, subdivision, or component of another larger entity.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
E.
historicalPeg
Indicates a relationship where one entity’s value, status, or definition was formerly fixed or tied to another entity in the past.
- 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_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. |
Created at: March 1, 2026, 7:59 p.m.