Triple
T27214889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gajsinghpur |
E684111
|
entity |
| Predicate | borderAreaSignificance |
P96125
|
FINISHED |
| Object | Located in a sensitive border region |
—
|
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: Located in a sensitive border region | Statement: [Gajsinghpur, borderAreaSignificance, Located in a sensitive border region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderAreaSignificance Context triple: [Gajsinghpur, borderAreaSignificance, Located in a sensitive border region]
-
A.
borderSignificance
chosen
Indicates the degree of importance, impact, or relevance that a particular border or boundary has in a given context or relationship.
-
B.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
C.
hasBorderSignificance
Indicates that a border between entities holds particular importance, impact, or relevance in a given context.
-
D.
borderCharacteristic
Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
-
E.
significanceArea
Indicates that a specified area holds particular importance, relevance, or impact within a given context or system.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 27, 2026, 9:41 a.m.