Triple
T32495994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN Security Council Resolution 476 |
E830524
|
entity |
| Predicate | callsOnAllStatesTo |
P2350
|
FINISHED |
| Object | not recognize any changes in the status of Jerusalem |
—
|
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: not recognize any changes in the status of Jerusalem | Statement: [UN Security Council Resolution 476, callsOnAllStatesTo, not recognize any changes in the status of Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callsOnAllStatesTo Context triple: [UN Security Council Resolution 476, callsOnAllStatesTo, not recognize any changes in the status of Jerusalem]
-
A.
callsFor
chosen
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
B.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
C.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
D.
calledBy
Indicates that one entity initiates a call or invocation to another entity.
-
E.
canBeCalledTo
Indicates that one entity is able or permitted to initiate a call or summon another entity.
- F. None of above.
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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:59 a.m.