Triple
T28883668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangaon (Lok Sabha constituency) |
E732491
|
entity |
| Predicate | includesBorderArea |
P108581
|
FINISHED |
| Object | Petrapole |
—
|
NE NERFINISHED |
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: Petrapole | Statement: [Bangaon (Lok Sabha constituency), includesBorderArea, Petrapole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBorderArea Context triple: [Bangaon (Lok Sabha constituency), includesBorderArea, Petrapole]
-
A.
containsBorder
Indicates that one entity has a boundary or edge that encloses, touches, or defines the perimeter of another entity.
-
B.
borderArea
chosen
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
C.
hasBorderAreaCharacteristics
Indicates that something possesses features or qualities typical of a border area between regions or territories.
-
D.
hasBorderAreaStatus
Indicates that an entity has a designated status related to being in or associated with a border area.
-
E.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
Created at: April 28, 2026, 7:47 a.m.