Triple
T26025333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allon Plan |
E647273
|
entity |
| Predicate | intendedPartner |
P167733
|
FINISHED |
| Object | Hashemite Kingdom of Jordan |
—
|
NE NERFINISHED |
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: Hashemite Kingdom of Jordan | Statement: [Allon Plan, intendedPartner, Hashemite Kingdom of Jordan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPartner Context triple: [Allon Plan, intendedPartner, Hashemite Kingdom of Jordan]
-
A.
partnerInUnionWith
Indicates a mutual partnership or union relationship between two entities, such as a civil, domestic, or similar legally or socially recognized union.
-
B.
symbolicPartnerOf
Indicates a relationship in which two entities are formally or representationally associated as partners in a symbolic, rather than practical or operational, sense.
-
C.
lifePartnerType
Indicates the type or category of a person’s life partner in a long-term or committed relationship.
-
D.
partnerInDiscovery
Indicates that two or more entities collaborated as partners in making a particular discovery.
-
E.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 22, 2026, 9:05 a.m.