Triple
T12365112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Bank of Syria |
E294839
|
entity |
| Predicate | ISO4217CurrencyCode |
P208
|
FINISHED |
| Object | SYP |
E60986
|
NE 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: SYP | Statement: [Central Bank of Syria, ISO4217CurrencyCode, SYP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SYP Context triple: [Central Bank of Syria, ISO4217CurrencyCode, SYP]
-
A.
SYP
chosen
SYP is the ISO 4217 currency code for the Syrian pound, the official monetary unit of Syria.
-
B.
SYR
SYR is the three-letter ISO 3166-1 alpha-3 country code representing the Middle Eastern nation of Syria.
-
C.
Sy
Sy is the first name of Sy Gomberg, an American screenwriter and producer known for his work in mid-20th-century film and television.
-
D.
Sy
Sy is a Diameter-based interface in telecommunications networks used for policy and charging control between the PCRF and online charging systems.
-
E.
SY
SY is a UK postcode area covering Shrewsbury and surrounding parts of Shropshire and nearby counties in western England and the Welsh border region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa3f958819080555bcae9958a53 |
completed | April 10, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62abbaaec8190b388d9dff999da8d |
completed | May 2, 2026, 4:47 p.m. |
Created at: April 8, 2026, 9:54 p.m.