Triple
T25445644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolkata–Mumbai highway |
E637628
|
entity |
| Predicate | linksEconomicCenter |
P158526
|
FINISHED |
| Object | Kolkata |
—
|
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: Kolkata | Statement: [Kolkata–Mumbai highway, linksEconomicCenter, Kolkata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksEconomicCenter Context triple: [Kolkata–Mumbai highway, linksEconomicCenter, Kolkata]
-
A.
economicLink
Indicates a relationship where entities are connected through economic interactions, dependencies, or exchanges such as trade, investment, or financial flows.
-
B.
isEconomicCenter
Indicates that an entity functions as a primary hub for economic activity, such as trade, finance, or industry, within a region or system.
-
C.
regionalEconomyActivity
Indicates the type or level of economic activity occurring within a specific geographic region.
-
D.
connectsCapitalWith
Indicates a relationship where something serves as a link or route between a capital city and another place or entity.
-
E.
linkedCity
Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f70346cc8190b7ed6b5a86a508cd |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:01 p.m.