Triple
T21815449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lihir people |
E538594
|
entity |
| Predicate | marineTenureSystem |
P72521
|
FINISHED |
| Object | customary marine tenure |
—
|
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: customary marine tenure | Statement: [Lihir people, marineTenureSystem, customary marine tenure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marineTenureSystem Context triple: [Lihir people, marineTenureSystem, customary marine tenure]
-
A.
seaTenureSystem
chosen
Indicates a system governing rights, access, and control over the use and management of marine or sea areas.
-
B.
managedForFisheriesBy
Indicates that the management or oversight of fisheries-related activities or resources is carried out by a specified agent or authority.
-
C.
landTenure
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
D.
hasExclusiveFishingRightsWithin
Indicates that one party holds sole legal authority to fish within a specified area, excluding others from exercising the same rights there.
-
E.
marineProtectedAreaAccess
Indicates that an entity has permission or ability to enter, use, or traverse a designated marine protected area under specified rules or restrictions.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc99bbc8190bf074930f361af7d |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.