Triple
T37951393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | old Israeli shekel |
E946753
|
entity |
| Predicate | withdrawnFromCirculation |
P189661
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [old Israeli shekel, withdrawnFromCirculation, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawnFromCirculation Context triple: [old Israeli shekel, withdrawnFromCirculation, 1985]
-
A.
withdrawn
Indicates that an entity has removed or taken back a previously offered, submitted, or available item, action, or commitment.
-
B.
isNonCirculating
Indicates that the entity is not intended for regular distribution, exchange, or circulation within its usual system or network.
-
C.
withdrawnAsStandard
Indicates that a previously recognized standard has been officially withdrawn and is no longer in active use or recommended status.
-
D.
withdrawnDuring
Indicates that something is removed, canceled, or taken back over the course of a specified time period or event.
-
E.
hasPrintCirculation
Indicates that an entity distributes or is available through a physical (printed) circulation, such as printed copies or issues.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc7b6c2c88190ad4f58980834053c |
completed | May 6, 2026, 10:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.