Triple
T26942203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Sindh |
E678549
|
entity |
| Predicate | capitalCityInModernEra |
P154833
|
FINISHED |
| Object | Karachi |
—
|
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: Karachi | Statement: [History of Sindh, capitalCityInModernEra, Karachi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityInModernEra Context triple: [History of Sindh, capitalCityInModernEra, Karachi]
-
A.
capitalFoundedModernName
Indicates that the capital city was founded under a different historical name than the one it is known by in modern times.
-
B.
historicalCapitalNow
Indicates that a location currently serves as the capital of an entity for which it also held capital status at some point in the past.
-
C.
modernCityCorrespondsToCapital
chosen
Indicates that a modern city serves as, or corresponds to, the capital of a given political or administrative entity.
-
D.
capitalCityObservedIn
Indicates that a particular capital city was observed, recorded, or identified within a specified context, location, or time frame.
-
E.
capitalPresentDayLocation
Indicates that the predicate specifies the present-day geographic location of a capital city.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 6:19 a.m.