Triple
T718262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahmedabad |
E14357
|
entity |
| Predicate | populationRankInIndia |
P1169
|
FINISHED |
| Object | one of the largest cities in India |
—
|
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: one of the largest cities in India | Statement: [Ahmedabad, populationRankInIndia, one of the largest cities in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInIndia Context triple: [Ahmedabad, populationRankInIndia, one of the largest cities in India]
-
A.
rankByLengthInIndia
Indicates an ordering of items based on their length specifically within the context or boundaries of India.
-
B.
populationRank
chosen
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
C.
hasPopulationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
D.
areaRank
Indicates the relative ordering or position of an entity based on the size of its area compared to others.
-
E.
countryRankContext
Indicates the relative position or ranking of a country within a specified contextual framework (such as economic, political, or performance-based criteria).
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a577658881909c12951d63d96377 |
completed | March 1, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f38898819089d79bad4f4ff2d2 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.