Triple
T24845993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Majete Wildlife Reserve |
E621747
|
entity |
| Predicate | coManagementAgreementSigned |
P55891
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Majete Wildlife Reserve, coManagementAgreementSigned, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coManagementAgreementSigned Context triple: [Majete Wildlife Reserve, coManagementAgreementSigned, 2003]
-
A.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
B.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
C.
rightsAgreementSignedWith
chosen
Indicates that a formal rights agreement has been executed and signed between two parties.
-
D.
agencySignedWith
Indicates that a formal agreement or contract has been established between an agency and another party.
-
E.
establishedByAgreementSignedIn
Indicates that something was formally created or instituted as a result of an agreement that was signed at a specific time or place.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:19 a.m.