Triple
T28834052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qusra |
E728128
|
entity |
| Predicate | hasDeJureClaimant |
P176013
|
FINISHED |
| Object | State of Palestine |
—
|
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: State of Palestine | Statement: [Qusra, hasDeJureClaimant, State of Palestine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeJureClaimant Context triple: [Qusra, hasDeJureClaimant, State of Palestine]
-
A.
claimedDeJureBy
chosen
Indicates that an entity is asserted, according to law or formal right, to have legitimate sovereignty or authority over another entity, regardless of actual control.
-
B.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
C.
supportedClaimant
Indicates that one entity has provided assistance, backing, or advocacy in favor of another entity who is making a claim or seeking a benefit.
-
D.
legalAuthorityClaimedBy
Indicates that one party asserts or claims to possess legal authority, power, or jurisdiction over another party or matter.
-
E.
governedByClaimant
Indicates that an entity is under the authority, control, or jurisdiction of a specified claimant.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 6:38 a.m.