Triple
T30886534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riau Islands Regency |
E786781
|
entity |
| Predicate | isMaritimeRegion |
P170271
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Riau Islands Regency, isMaritimeRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMaritimeRegion Context triple: [Riau Islands Regency, isMaritimeRegion, true]
-
A.
isPartOfMaritimeZone
Indicates that one area or feature is contained within, or legally belongs to, a specified maritime zone.
-
B.
nauticalRegion
Indicates that one entity is a maritime or nautical area within which the other entity is located, operates, or is relevant.
-
C.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
-
D.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
-
E.
isCoastalRegion
Indicates that a region is located along or directly adjacent to a sea or ocean coastline.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69206481881909e9f3d0e59c5b889 |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:49 p.m.