Triple
T28009262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java–Sumatra transport corridor |
E707367
|
entity |
| Predicate | keyPortOnJava |
P22777
|
FINISHED |
| Object | Port of Merak |
E519494
|
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: Port of Merak | Statement: [Java–Sumatra transport corridor, keyPortOnJava, Port of Merak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyPortOnJava Context triple: [Java–Sumatra transport corridor, keyPortOnJava, Port of Merak]
-
A.
keyPort
chosen
Indicates that a port serves as a primary or central connection point in a system or network.
-
B.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
C.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
D.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
E.
exportPort
Indicates the port or harbor from which goods, resources, or data are sent out from one location or entity to another.
- F. None of above.
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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63bd9241c8190af8074df6ead4b4b |
completed | May 2, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15b89cf624819086c0a0f34a6b0756 |
completed | May 26, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:02 p.m.