Triple
T28009263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java–Sumatra transport corridor |
E707367
|
entity |
| Predicate | keyPortOnSumatra |
P110393
|
FINISHED |
| Object | Port of Bakauheni |
—
|
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: Port of Bakauheni | Statement: [Java–Sumatra transport corridor, keyPortOnSumatra, Port of Bakauheni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyPortOnSumatra Context triple: [Java–Sumatra transport corridor, keyPortOnSumatra, Port of Bakauheni]
-
A.
keyPort
Indicates that a port serves as a primary or central connection point in a system or network.
-
B.
portOnIsland
chosen
Indicates that a port is located on, or belongs to, a particular island.
-
C.
keyFortress
Indicates that one entity functions as a key or means of access, control, or unlocking for a particular fortress or strongly secured place represented by the other entity.
-
D.
имаКамбанария
Indicates that a building or structure possesses a bell tower as one of its architectural features.
-
E.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:02 p.m.