Triple
T864946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman lira |
E18680
|
entity |
| Predicate | scriptUsedOnCoins |
P20456
|
FINISHED |
| Object | Arabic script |
—
|
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: Arabic script | Statement: [Ottoman lira, scriptUsedOnCoins, Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptUsedOnCoins Context triple: [Ottoman lira, scriptUsedOnCoins, Arabic script]
-
A.
coinagePower
Indicates the authority or capacity of an entity to create, issue, or regulate currency or coinage.
-
B.
coinedIn
Indicates that something (typically a term, phrase, or name) was first created or introduced at a particular time or in a particular place.
-
C.
authorizedCoinMetal
Indicates that a particular metal is officially approved for use in minting a given coin.
-
D.
usedByDenomination
Indicates that something (such as an object, practice, or concept) is employed or utilized by a particular religious denomination.
-
E.
coinIssuer
Indicates that an entity issues, mints, or is responsible for the creation and release of a particular coin or currency.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac6acc148190bcc00a1e939ace77 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa86065881909d477e26fdd84d45 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab797b1081908f034d216649bb83 |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:39 p.m.