Triple
T14720310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palestinian Authority |
E345794
|
entity |
| Predicate | hasLimitedSovereignty |
P5545
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Palestinian Authority, hasLimitedSovereignty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedSovereignty Context triple: [Palestinian Authority, hasLimitedSovereignty, true]
-
A.
sovereigntyStatus
chosen
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
B.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over another entity.
-
C.
hasSovereignPowerOver
Indicates that one entity holds ultimate governing authority or supreme ruling power over another entity.
-
D.
hasTerritorialPossession
Indicates that one entity holds ownership, control, or legal rights over a specific territory or geographic area.
-
E.
hasLimitedAutonomyIn
Indicates that an entity operates or makes decisions within a domain where its freedom of action is constrained or controlled by another entity or governing context.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98823408190b4b58a4c4a3fa3a3 |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.