Triple
T26714983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgaria–Turkey border |
E673524
|
entity |
| Predicate | currencyOnOneSide |
P26642
|
FINISHED |
| Object | Bulgarian lev |
—
|
NE NERFINISHED |
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: Bulgarian lev | Statement: [Bulgaria–Turkey border, currencyOnOneSide, Bulgarian lev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyOnOneSide Context triple: [Bulgaria–Turkey border, currencyOnOneSide, Bulgarian lev]
-
A.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
-
B.
currencyNotUnified
chosen
Indicates that the entities involved do not share a single common currency or monetary system.
-
C.
currencyOnboard
Indicates that a particular currency has been enabled, registered, or made available for use within a given system or context.
-
D.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
E.
currencyOversight
Indicates that an entity has authority or responsibility to supervise, regulate, or manage the use, issuance, or stability of a currency.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 3:37 a.m.