Triple
T25674629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakdwip |
E643771
|
entity |
| Predicate | hasNearbyPortOrJetty |
P63633
|
FINISHED |
| Object | Kakdwip jetty |
—
|
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: Kakdwip jetty | Statement: [Kakdwip, hasNearbyPortOrJetty, Kakdwip jetty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyPortOrJetty Context triple: [Kakdwip, hasNearbyPortOrJetty, Kakdwip jetty]
-
A.
hasNearbyPortAccess
chosen
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
-
B.
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).
-
C.
isPortFor
Indicates that one entity serves as a port, interface, or connection point for another entity.
-
D.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
-
E.
hasNearbyPortionOf
Indicates that one entity has a portion that is spatially close to, but not necessarily touching, another entity or region.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 21, 2026, 7:34 p.m.