Triple
T32751044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Java northern railway line |
E837495
|
entity |
| Predicate | connectsToPortRegions |
P24718
|
FINISHED |
| Object | Tanjung Priok area |
—
|
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: Tanjung Priok area | Statement: [Java northern railway line, connectsToPortRegions, Tanjung Priok area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToPortRegions Context triple: [Java northern railway line, connectsToPortRegions, Tanjung Priok area]
-
A.
connectsPortRegion
Indicates that one entity serves as a linkage or interface between a specific port and a defined region.
-
B.
isPortRegionOf
Indicates that a region functions as the port area associated with, or belonging to, a particular larger geographic or administrative entity.
-
C.
connectsRegions
chosen
Indicates a relationship where one entity links or joins two or more distinct regions, enabling passage, interaction, or continuity between them.
-
D.
connectsPortToHinterland
Indicates that a port serves as a transport or logistical link to its surrounding inland (hinterland) region.
-
E.
linkedToPort
Indicates that one entity is connected or associated with a specific port, such as a network, hardware, or interface port.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:12 a.m.