Triple
T27324589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulau Kecil |
E689605
|
entity |
| Predicate | maritimeTerritoryOf |
P16387
|
FINISHED |
| Object | Indonesia |
—
|
NE NERFINISHED |
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: Indonesia | Statement: [Pulau Kecil, maritimeTerritoryOf, Indonesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeTerritoryOf Context triple: [Pulau Kecil, maritimeTerritoryOf, Indonesia]
-
A.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
-
B.
maritimeBoundaryLengthApproxKm
Indicates the approximate length, measured in kilometers, of a state's maritime boundary or coastline.
-
C.
maximumBreadthOfTerritorialSea
Indicates the greatest legally defined width of a state's territorial sea measured from its baseline.
-
D.
borderingCountryOfTerritory
Indicates that one country shares a land or maritime boundary with the specified territory.
-
E.
seaAreaManagedBy
chosen
Indicates that a specified sea area falls under the management, control, or administrative responsibility of a particular authority or 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:35 a.m.