Triple
T4261043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Commissioner for Palestine and Transjordan |
E96103
|
entity |
| Predicate | confersPowerTo |
P7884
|
FINISHED |
| Object | issue ordinances |
—
|
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: issue ordinances | Statement: [High Commissioner for Palestine and Transjordan, confersPowerTo, issue ordinances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confersPowerTo Context triple: [High Commissioner for Palestine and Transjordan, confersPowerTo, issue ordinances]
-
A.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
B.
grantedPower
chosen
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
C.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
D.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
E.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f8103b48190934a810faafa6cb7 |
completed | March 12, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.