Triple
T34651229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanquelim |
E889842
|
entity |
| Predicate | belongsToDistrictType |
P176124
|
FINISHED |
| Object | district |
—
|
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: district | Statement: [Sanquelim, belongsToDistrictType, district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDistrictType Context triple: [Sanquelim, belongsToDistrictType, district]
-
A.
belongsToDistrictLevelCity
Indicates that an entity is administratively part of, or falls under the jurisdiction of, a specific district-level city.
-
B.
withinDistrictType
chosen
Indicates that one entity is located inside or falls under the jurisdiction of a specific type or category of district.
-
C.
belongsToDistrictBeforeCityStatus
Indicates that an entity was part of a specific district prior to the area being granted city status.
-
D.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
E.
hasRelatedDistrict
Indicates that one entity is associated with, linked to, or falls within the scope of a particular district.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 1, 2026, 2:04 a.m.