Triple
T33843284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meriam people |
E867410
|
entity |
| Predicate | legalRecognitionOfLandRights |
P182365
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Meriam people, legalRecognitionOfLandRights, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRecognitionOfLandRights Context triple: [Meriam people, legalRecognitionOfLandRights, 1992]
-
A.
legalRecognition
Indicates that an authority formally acknowledges the validity, status, or rights associated with an entity, relationship, or action under the law.
-
B.
landTenure
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
C.
landRightsMilestone
chosen
Indicates a significant event or achievement related to the recognition, transfer, or formalization of rights to use, control, or own land between parties.
-
D.
landPolicy
Indicates a relationship where an authority defines or applies rules governing the ownership, use, management, or distribution of land.
-
E.
landAdministrationSystem
Indicates a system or framework through which land rights, ownership, use, and related records are formally managed, recorded, and regulated.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 1, 2026, 1:47 a.m.