Triple
T9852412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peel Commission partition proposal |
E239498
|
entity |
| Predicate | reasonForInquiry |
P24494
|
FINISHED |
| Object | unrest in Mandatory Palestine |
—
|
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: unrest in Mandatory Palestine | Statement: [Peel Commission partition proposal, reasonForInquiry, unrest in Mandatory Palestine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForInquiry Context triple: [Peel Commission partition proposal, reasonForInquiry, unrest in Mandatory Palestine]
-
A.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
B.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
C.
inquiry
Indicates that one entity seeks information, clarification, or an answer from another through a question or request.
-
D.
commissionReason
Indicates the reason or justification for which a commission is initiated, assigned, or granted between entities.
-
E.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb375ba448190a32cca2b0f376ac1 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:34 p.m.