Triple
T34590478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port system of Indonesia |
E888167
|
entity |
| Predicate | includesPortAuthority |
P205476
|
FINISHED |
| Object | Pelindo |
E2024301
|
NE 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: Pelindo | Statement: [Port system of Indonesia, includesPortAuthority, Pelindo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPortAuthority Context triple: [Port system of Indonesia, includesPortAuthority, Pelindo]
-
A.
includesPort
Indicates that one entity contains, encompasses, or has as part of it a specific port or set of ports.
-
B.
portAuthorityType
Indicates the classification or category of a port authority based on its organizational or administrative type.
-
C.
hasPortCity
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
D.
isHomePortOf
Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
-
E.
hasPortDistrict
Indicates that an entity is associated with or located within a specific port district.
- F. None of above. chosen
Provenance (5 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37363f21a48190a7d371f4a50d27f7 |
completed | June 21, 2026, 12:54 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:03 a.m.