Triple
T16400061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ਧੁਡੀਕੇ |
E398286
|
entity |
| Predicate | ruralSettlementType |
P36501
|
FINISHED |
| Object | ਪੰਜਾਬੀ ਪਿੰਡ |
—
|
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: ਪੰਜਾਬੀ ਪਿੰਡ | Statement: [ਧੁਡੀਕੇ, ruralSettlementType, ਪੰਜਾਬੀ ਪਿੰਡ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruralSettlementType Context triple: [ਧੁਡੀਕੇ, ruralSettlementType, ਪੰਜਾਬੀ ਪਿੰਡ]
-
A.
humanSettlementType
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
B.
isRuralSettlement
chosen
Indicates that a settlement is located in a rural area, typically characterized by low population density and limited urban infrastructure.
-
C.
historicalSettlementType
Indicates the type or category of settlement an entity was historically classified as (e.g., village, town, city) during a past period.
-
D.
traditionalSettlement
Indicates that an entity is a settlement characterized by long-established, customary, or historically rooted patterns of habitation and land use.
-
E.
traditionalSettlementArea
Indicates that an area is recognized as a traditional settlement zone associated with a particular group or community.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327cea4e481908400b852a5a7032a |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.