Triple
T2744078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian lev |
E60822
|
entity |
| Predicate | introducedInCurrentForm |
P763
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Bulgarian lev, introducedInCurrentForm, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInCurrentForm Context triple: [Bulgarian lev, introducedInCurrentForm, 1999]
-
A.
establishedInCurrentForm
chosen
Indicates the point in time when something took on its present structure, organization, or configuration, distinct from any earlier versions or forms.
-
B.
establishedInCurrentFormBy
Indicates that one entity created, organized, or defined another entity in the specific structure or configuration in which it currently exists.
-
C.
containsForm
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
D.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
E.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb32ef74819096ae399d16d4f31d |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.