Triple

T531895
Position Surface form Disambiguated ID Type / Status
Subject Bombay Castle E12239 entity
Predicate historicalCoreOf P16505 FINISHED
Object Fort area business district of Mumbai 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: Fort area business district of Mumbai | Statement: [Bombay Castle, historicalCoreOf, Fort area business district of Mumbai]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalCoreOf
Context triple: [Bombay Castle, historicalCoreOf, Fort area business district of Mumbai]
  • A. historicallyExtendedBy
    Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
  • B. historicalFunction
    Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
  • C. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • D. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • E. historicalReference
    Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
  • 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_69a4933208e88190891f5debab1b776d completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4985e51908190a34aa82ea9dbee1e completed March 1, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69a494b257108190a537dffbb9d621b5 completed March 1, 2026, 7:34 p.m.
PDg Predicate description generation batch_69a49857e1148190aa782b82675cf0b5 completed March 1, 2026, 7:49 p.m.
Created at: March 1, 2026, 7:32 p.m.