Triple
T4503087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman kuruş |
E101268
|
entity |
| Predicate | valueRelativeToAkçe |
P56936
|
FINISHED |
| Object | 1 kuruş = 40 para = 120 akçe (initially) |
—
|
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: 1 kuruş = 40 para = 120 akçe (initially) | Statement: [Ottoman kuruş, valueRelativeToAkçe, 1 kuruş = 40 para = 120 akçe (initially)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueRelativeToAkçe Context triple: [Ottoman kuruş, valueRelativeToAkçe, 1 kuruş = 40 para = 120 akçe (initially)]
-
A.
valueInPula
Indicates that one entity represents the monetary value of another entity expressed in Botswana pula.
-
B.
valueInUSD
Indicates that a given amount or asset is expressed or evaluated in terms of its monetary value in United States dollars (USD).
-
C.
valueRelativeToGuilder
Indicates that something’s value is expressed in terms of, or compared relative to, the guilder currency.
-
D.
valueInFrancs
Indicates that a specified monetary amount is expressed or measured in French francs.
-
E.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fb2bec8190b74b6a49d9475514 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:01 p.m.