Triple
T32292125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passfield White Paper |
E824989
|
entity |
| Predicate | mandateTerritory |
P94456
|
FINISHED |
| Object | 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: Palestine | Statement: [Passfield White Paper, mandateTerritory, Palestine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandateTerritory Context triple: [Passfield White Paper, mandateTerritory, Palestine]
-
A.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
B.
missionTerritoryOf
chosen
Indicates that a specified territory is under the jurisdiction or scope of a particular mission.
-
C.
affectsTerritoryOf
Indicates that one entity causes changes to, or has an impact on, the territorial domain or jurisdiction of another entity.
-
D.
governedTerritory
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
-
E.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd3500608190ba9e172c0458ff9f |
completed | May 3, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:44 a.m.