Triple
T29274340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Embassy in Jerusalem |
E742207
|
entity |
| Predicate | moveMarked |
P34686
|
FINISHED |
| Object | shift in U.S. policy on Jerusalem’s status |
—
|
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: shift in U.S. policy on Jerusalem’s status | Statement: [U.S. Embassy in Jerusalem, moveMarked, shift in U.S. policy on Jerusalem’s status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moveMarked Context triple: [U.S. Embassy in Jerusalem, moveMarked, shift in U.S. policy on Jerusalem’s status]
-
A.
marksShiftToward
chosen
Indicates a change or transition from one state, condition, or position toward another, highlighting the direction or trend of that shift.
-
B.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
C.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
D.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
E.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 12:50 p.m.