Triple
T7887044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India–Pakistan border |
E183127
|
entity |
| Predicate | hasBorderFencing |
P14204
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [India–Pakistan border, hasBorderFencing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderFencing Context triple: [India–Pakistan border, hasBorderFencing, yes]
-
A.
hasBorderWallOrFence
chosen
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
B.
hasBorderFacilities
Indicates that one entity possesses or is equipped with facilities or infrastructure used for managing or servicing a border with another entity.
-
C.
hasBorderFacilityType
Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
-
D.
numberOfFences
Indicates the quantity of fences associated with or present around a given entity.
-
E.
bordersFacility
Indicates that one facility or site lies directly adjacent to and shares a boundary with another facility.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39d97460819089e37169813af5c2 |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:59 p.m.