Triple
T9473007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Ambassador to Israel |
E228439
|
entity |
| Predicate | seatMoveEffectiveDate |
P70817
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [United States Ambassador to Israel, seatMoveEffectiveDate, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatMoveEffectiveDate Context triple: [United States Ambassador to Israel, seatMoveEffectiveDate, 2018]
-
A.
UNSeatTransferDate
Indicates the date on which a seat is transferred from one holder to another.
-
B.
movementDate
Indicates the date on which a movement, transfer, or relocation event occurs.
-
C.
decisionEffectiveDate
Indicates the date on which a particular decision becomes valid, operative, or officially takes effect.
-
D.
retrocessionDate
Indicates the date on which rights, obligations, or control previously transferred are formally returned or reassigned back to the original party or another designated party.
-
E.
officeTransferredAt
chosen
Indicates the time or date at which an office (or official position) was transferred from one holder or location to another.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7ff0afd08190871b68a88fdbff2b |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.