Triple
T4503096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman kuruş |
E101268
|
entity |
| Predicate | usedAsAccountingUnitAfterReform |
P56938
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ottoman kuruş, usedAsAccountingUnitAfterReform, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsAccountingUnitAfterReform Context triple: [Ottoman kuruş, usedAsAccountingUnitAfterReform, yes]
-
A.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
B.
hasReformedForm
Indicates that an entity has a later, modified, or updated form that results from a process of reform or restructuring.
-
C.
reintroducedCurrencyOf
Indicates that a currency has been brought back into use as legal tender in a particular country or region after having been previously replaced, discontinued, or suspended.
-
D.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
E.
nowAdministeredAsPartOf
Indicates that something is currently being given or managed as a component of a larger treatment, program, or regimen.
- 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.