Triple
T17881820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiunga |
E447103
|
entity |
| Predicate | servesAsPortFor |
P92400
|
FINISHED |
| Object | Fly River shipping |
—
|
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: Fly River shipping | Statement: [Kiunga, servesAsPortFor, Fly River shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsPortFor Context triple: [Kiunga, servesAsPortFor, Fly River shipping]
-
A.
isPortFor
chosen
Indicates that one entity serves as a port, interface, or connection point for another entity.
-
B.
refersToPort
Indicates that one entity designates, points to, or is associated with a specific port (such as a network, hardware, or logical port).
-
C.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
D.
servesAsGatewayTo
Indicates that one entity functions as an entry point, access route, or intermediary channel that enables reaching or connecting to another entity.
-
E.
servedPorts
Indicates that a network service or device makes specific ports available to accept incoming connections or traffic.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c0f40fc8190b2e615b41829f5df |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.