Triple
T25674602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakdwip |
E643771
|
entity |
| Predicate | coastalHub |
P159179
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kakdwip, coastalHub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalHub Context triple: [Kakdwip, coastalHub, true]
-
A.
areCoastal
Indicates that the entities are located on or adjacent to a coastline or seashore.
-
B.
coastalCluster
Indicates a grouping of entities that are located near or along the same coastal area or shoreline.
-
C.
coastalInteraction
Indicates an interaction or relationship occurring between entities and a coastal environment, such as along shorelines or near the sea.
-
D.
coastalPeople
Indicates that the people are located in, originate from, or are closely associated with a coastal (seaside) area.
-
E.
connectsToCoastAt
Indicates that one entity has a direct physical or geographical connection or access to a coastline at the location of another entity.
- F. None of above. chosen
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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3535808190bb1843eb32cd2c4e |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 7:34 p.m.