Triple
T19217063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zona Ekonomi Eksklusif Indonesia |
E480512
|
entity |
| Predicate | memberikanHak |
P74042
|
FINISHED |
| Object | hak berdaulat kepada Indonesia |
—
|
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: hak berdaulat kepada Indonesia | Statement: [Zona Ekonomi Eksklusif Indonesia, memberikanHak, hak berdaulat kepada Indonesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberikanHak Context triple: [Zona Ekonomi Eksklusif Indonesia, memberikanHak, hak berdaulat kepada Indonesia]
-
A.
mayGrant
chosen
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
B.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
C.
hadRight
Indicates that an entity possessed a legal or moral entitlement to perform an action, access something, or claim something in relation to another entity or situation.
-
D.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
E.
grantedAs
Indicates that one entity is conferred, assigned, or bestowed in a particular role, status, or capacity to another entity.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3aff9c8190974363683b8246f5 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:23 p.m.