Triple
T282853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palestinian Legislative Council |
E5825
|
entity |
| Predicate | reasonForInactivity |
P7401
|
FINISHED |
| Object | Fatah–Hamas political split |
—
|
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: Fatah–Hamas political split | Statement: [Palestinian Legislative Council, reasonForInactivity, Fatah–Hamas political split]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForInactivity Context triple: [Palestinian Legislative Council, reasonForInactivity, Fatah–Hamas political split]
-
A.
suspensionReason
chosen
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
B.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
C.
reasonForReoffer
Indicates the reason or justification for presenting something again after it was previously offered.
-
D.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
E.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e0c14b48190a5c936bab36180b3 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.