Triple
T35785631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | coat of arms of Israel |
E1034555
|
entity |
| Predicate | governmentResolutionYear |
P203797
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [coat of arms of Israel, governmentResolutionYear, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentResolutionYear Context triple: [coat of arms of Israel, governmentResolutionYear, 1949]
-
A.
UNResolutionYear
Indicates the calendar year in which a specific United Nations resolution was formally adopted or issued.
-
B.
congressionalApprovalYear
Indicates the year in which a given item, action, or measure received formal approval by a legislative congress.
-
C.
yearOfPromulgation
Indicates the specific year in which something, typically a law or formal decree, was officially enacted or put into effect.
-
D.
policyAnnouncementYear
Indicates the year in which a specific policy was formally announced.
-
E.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0205c0bff481908238a382459b3a93 |
completed | May 11, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_6a0205143f20819087ee31576835be26 |
completed | May 11, 2026, 4:34 p.m. |
| PDg | Predicate description generation | batch_6a0205bfab208190982728a690ce183d |
completed | May 11, 2026, 4:37 p.m. |
Created at: May 3, 2026, 4:06 p.m.