Triple
T28834193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qaryut |
E728132
|
entity |
| Predicate | hasAreaControlRegime |
P63323
|
FINISHED |
| Object | Israeli occupation |
—
|
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: Israeli occupation | Statement: [Qaryut, hasAreaControlRegime, Israeli occupation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAreaControlRegime Context triple: [Qaryut, hasAreaControlRegime, Israeli occupation]
-
A.
regulatesArea
Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
-
B.
regulatedArea
chosen
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
C.
hasAccessRegime
Indicates that one entity is subject to, governed by, or managed under a particular access control regime or set of access rules defined by another entity.
-
D.
hasAutonomousArea
Indicates that an entity possesses or contains a geographically or administratively distinct area that has a degree of self-governance or autonomy.
-
E.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
- 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_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 28, 2026, 6:38 a.m.