Triple
T11143898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-Jordanian Treaty 1948 |
E263625
|
entity |
| Predicate | signingPartOf |
P52847
|
FINISHED |
| Object | post–World War II decolonization |
—
|
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: post–World War II decolonization | Statement: [Anglo-Jordanian Treaty 1948, signingPartOf, post–World War II decolonization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signingPartOf Context triple: [Anglo-Jordanian Treaty 1948, signingPartOf, post–World War II decolonization]
-
A.
isSignedAlong
Indicates that an entity has signed or endorsed something in conjunction with another specified entity.
-
B.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
C.
consideredPartOf
chosen
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
D.
signedTogetherWith
Indicates that one entity signed a document, agreement, or contract jointly with another entity.
-
E.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8634d5481909b114d30a542ea3f |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.