Triple
T31841549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty between Spain and Morocco of 1969 |
E812822
|
entity |
| Predicate | partyRoleOfMorocco |
P180067
|
FINISHED |
| Object | receiving state |
—
|
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: receiving state | Statement: [Treaty between Spain and Morocco of 1969, partyRoleOfMorocco, receiving state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyRoleOfMorocco Context triple: [Treaty between Spain and Morocco of 1969, partyRoleOfMorocco, receiving state]
-
A.
MoroccanRuler
Indicates a person holds or held the position of ruler over Morocco.
-
B.
MoroccanConcession
Indicates a diplomatic or commercial concession granted in the context of Moroccan affairs or territory.
-
C.
partyRoleOfSpain
Indicates that a specific role or capacity is held by Spain as a party within a given agreement, event, or context.
-
D.
MoroccanStrengthApprox
Indicates an approximate assessment or estimation of the strength associated with Morocco or Moroccan-related entities.
-
E.
statusInMauritania
Indicates the legal, social, or conservation status that an entity holds specifically within the context of Mauritania.
- F. None of above. chosen
Provenance (4 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 30, 2026, 11:49 p.m.