Triple
T30731167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan–US Free Trade Agreement |
E782426
|
entity |
| Predicate | dateRatifiedByJordan |
P16528
|
FINISHED |
| Object | 2001-05-13 |
—
|
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: 2001-05-13 | Statement: [Jordan–US Free Trade Agreement, dateRatifiedByJordan, 2001-05-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRatifiedByJordan Context triple: [Jordan–US Free Trade Agreement, dateRatifiedByJordan, 2001-05-13]
-
A.
unitJordan
Indicates that the subject is a Jordan block (or Jordan matrix) that has been normalized to have unit (typically 1) entries on its main diagonal.
-
B.
wasUnderJordanianControl
Indicates that, during a specified time period, the subject entity was governed, administered, or controlled by Jordanian authorities.
-
C.
ratifiedAt
chosen
Indicates the date, time, or event context at which an agreement, treaty, or formal decision was officially ratified.
-
D.
accessFromJordan
Indicates that an access or connection originates from, or is made within, Jordan.
-
E.
reignStartAsKingOfJordan
Indicates the date or event when a person began their reign as the king of Jordan.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68ee35f648190814a3d990dd74260 |
completed | May 2, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:37 p.m.