Triple
T19216941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segitiga Terumbu Karang |
E480509
|
entity |
| Predicate | rentanTerhadap |
P135014
|
FINISHED |
| Object | perubahan iklim |
—
|
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: perubahan iklim | Statement: [Segitiga Terumbu Karang, rentanTerhadap, perubahan iklim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rentanTerhadap Context triple: [Segitiga Terumbu Karang, rentanTerhadap, perubahan iklim]
-
A.
ransom
Indicates demanding payment or concessions in exchange for releasing a person, object, or information held under threat or coercion.
-
B.
resistedIn
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
C.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
reivindica
Indicates that an entity asserts a right to, claims ownership of, or demands recognition or restitution for something.
-
E.
heldToProtect
Indicates that one entity is kept in someone’s possession or custody for the purpose of safeguarding or protecting it.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:23 p.m.