Triple
T19217084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zona Ekonomi Eksklusif Indonesia |
E480512
|
entity |
| Predicate | wilayahMencakup |
P8868
|
FINISHED |
| Object | perairan di Samudra Hindia |
—
|
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: perairan di Samudra Hindia | Statement: [Zona Ekonomi Eksklusif Indonesia, wilayahMencakup, perairan di Samudra Hindia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wilayahMencakup Context triple: [Zona Ekonomi Eksklusif Indonesia, wilayahMencakup, perairan di Samudra Hindia]
-
A.
regionInMalaysia
Indicates that a region or area is located within the country of Malaysia.
-
B.
missionRegion
Indicates the geographic or administrative region in which a mission is carried out or assigned.
-
C.
missionTerritoryOf
Indicates that a specified territory is under the jurisdiction or scope of a particular mission.
-
D.
territorialExtent
chosen
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
E.
hasFederalTerritory
Indicates that a sovereign state possesses and administers one or more territories directly under its federal authority rather than as constituent states or provinces.
- 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.