Triple
T23523896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan and Israel |
E574580
|
entity |
| Predicate | leaseArrangementsEndedIn |
P20545
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Jordan and Israel, leaseArrangementsEndedIn, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseArrangementsEndedIn Context triple: [Jordan and Israel, leaseArrangementsEndedIn, 2019]
-
A.
leaseContext
Indicates the contextual circumstances, terms, or conditions under which a lease agreement or leasing relationship exists or is interpreted.
-
B.
tenantsEnd
chosen
Indicates that a tenancy or lease relationship between parties comes to an end at a specified time or under certain conditions.
-
C.
leaseBegan
Indicates that a lease agreement between parties started or came into effect at a specific time.
-
D.
leaseControversyWith
Indicates a dispute or conflict arising from the terms, conditions, or execution of a lease agreement between the related entities.
-
E.
reservationProvisionEndedBy
Indicates that the termination or conclusion of a reservation’s provision is caused or brought about by a specific agent or event.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac71ec8881909bfb706efdc2518f |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.