Triple
T27409450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kei people |
E692100
|
entity |
| Predicate | usesCustomaryMarineTenure |
P72521
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kei people, usesCustomaryMarineTenure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCustomaryMarineTenure Context triple: [Kei people, usesCustomaryMarineTenure, yes]
-
A.
appliesToTerritorialWatersOf
Indicates that something (such as a rule, status, or condition) is applicable within the territorial waters of a specified entity.
-
B.
shorelineOwnership
Indicates that one entity holds legal or recognized ownership rights over a stretch of shoreline associated with another entity or location.
-
C.
seaTenureSystem
chosen
Indicates a system governing rights, access, and control over the use and management of marine or sea areas.
-
D.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
E.
hasExclusiveFishingRightsWithin
Indicates that one party holds sole legal authority to fish within a specified area, excluding others from exercising the same rights there.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 12:31 p.m.