Triple
T22986328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan and Syria |
E571615
|
entity |
| Predicate | tradeStatus |
P14392
|
FINISHED |
| Object | trade volumes affected by conflict in Syria |
—
|
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: trade volumes affected by conflict in Syria | Statement: [Jordan and Syria, tradeStatus, trade volumes affected by conflict in Syria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeStatus Context triple: [Jordan and Syria, tradeStatus, trade volumes affected by conflict in Syria]
-
A.
tradeFrameworkStatus
Indicates the current state or condition of a trade framework within a given relationship or process.
-
B.
tradingStatus
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
-
C.
statusTransmission
Indicates that a status or state is being communicated or passed from one entity to another.
-
D.
profitStatus
Indicates the financial performance state of an entity, such as whether it is operating at a profit, loss, or breaking even.
-
E.
commercialStatus
chosen
Indicates the current state or condition of something in terms of its commercial availability, activity, or market use.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182996ee08190ab74014ee7ecac2b |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.