Triple
T25327796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VECC |
E635064
|
entity |
| Predicate | formerCityNameServed |
P75589
|
FINISHED |
| Object | Calcutta |
—
|
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: Calcutta | Statement: [VECC, formerCityNameServed, Calcutta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCityNameServed Context triple: [VECC, formerCityNameServed, Calcutta]
-
A.
formerNameOfCityServed
chosen
Indicates that one name was previously used for a city that is (or was) served by a particular entity, before being replaced by its current name.
-
B.
formerCityName
Indicates that an entity was previously known by a different city name in the past.
-
C.
formerCity
Indicates that an entity was once recognized as a city but no longer holds that status.
-
D.
cityPreviouslyLocatedIn
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
-
E.
formerCityContext
Indicates that the subject entity was formerly classified or recognized as a city within the specified contextual scope or time frame.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 21, 2026, 1:30 p.m.