Triple
T12891748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hajipur |
E308384
|
entity |
| Predicate | populationRankInBihar |
P107294
|
FINISHED |
| Object | one of the larger cities |
—
|
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 larger cities | Statement: [Hajipur, populationRankInBihar, one of the larger cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInBihar Context triple: [Hajipur, populationRankInBihar, one of the larger cities]
-
A.
populationRankInWestBengal
Indicates the relative position of an entity in terms of population size compared to other entities within West Bengal.
-
B.
rankByPopulationInIndia
Indicates the relative ordering of entities based on their population size within India.
-
C.
rankWithinBritishIndia
Indicates the relative hierarchical position or status an entity held within the administrative, military, or social ranking system of British India.
-
D.
rankByLengthInIndia
Indicates an ordering of items based on their length specifically within the context or boundaries of India.
-
E.
populationRankInTelangana
Indicates the relative position of an entity in terms of population size compared to other entities within Telangana.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97146d2208190be5ae26e51193b67 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:39 p.m.