Triple
T14782360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadaat-e-Amroha |
E347420
|
entity |
| Predicate | urbanRuralPresence |
P60791
|
FINISHED |
| Object | primarily urban in Amroha |
—
|
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: primarily urban in Amroha | Statement: [Sadaat-e-Amroha, urbanRuralPresence, primarily urban in Amroha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanRuralPresence Context triple: [Sadaat-e-Amroha, urbanRuralPresence, primarily urban in Amroha]
-
A.
urbanRuralSplit
Indicates a division or distinction between urban and rural areas, conditions, or populations.
-
B.
isRuralOrUrban
chosen
Indicates whether an entity is classified as being in a rural area or an urban area.
-
C.
hasUrbanRuralMix
Indicates that something exhibits a combination or blend of both urban and rural characteristics or components.
-
D.
hasRuralLocality
Indicates that an entity possesses, includes, or is associated with a rural locality (such as a village, hamlet, or countryside settlement) within its scope or jurisdiction.
-
E.
isRural
Indicates that something is located in, characteristic of, or associated with a countryside or non-urban area.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9de3f48190b7706925e2947cf5 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.