Triple
T23523901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan and Israel |
E574580
|
entity |
| Predicate | haveSigned |
P153095
|
FINISHED |
| Object | aviation agreements |
—
|
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: aviation agreements | Statement: [Jordan and Israel, haveSigned, aviation agreements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveSigned Context triple: [Jordan and Israel, haveSigned, aviation agreements]
-
A.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
B.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
C.
signedTo
Indicates that one entity has formally entered into a contract or agreement with another, typically for representation, employment, or services.
-
D.
isSigned
Indicates that an entity has been formally endorsed or authenticated through a signature or signing action.
-
E.
willSignedOn
Indicates that a person has formally signed a will on a specific date or occasion, thereby validating or executing that testamentary document.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:09 p.m.