Triple
T18581313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amungme people |
E454120
|
entity |
| Predicate | customaryLandTenure |
P34249
|
FINISHED |
| Object | clan-based ownership |
—
|
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: clan-based ownership | Statement: [Amungme people, customaryLandTenure, clan-based ownership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customaryLandTenure Context triple: [Amungme people, customaryLandTenure, clan-based ownership]
-
A.
landTenure
chosen
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
B.
seaTenureSystem
Indicates a system governing rights, access, and control over the use and management of marine or sea areas.
-
C.
landPolicy
Indicates a relationship where an authority defines or applies rules governing the ownership, use, management, or distribution of land.
-
D.
traditionalLandIncludes
Indicates that a specified traditional land area encompasses or contains another geographic area within its recognized boundaries.
-
E.
landConveyed
Indicates that ownership or rights to a piece of land have been legally transferred from one party to another.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543cffd34819090d636fd584f51db |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.